Contract call
Failed
unlock
0xfe…33e4b
SPJG…868RN
SP3Y…FQA4K.bridge
unlock
0xfe…33e4b
SPJG…868RN
SP3Y…FQA4K.bridge
Transaction failed
This transaction would have succeeded, but was rolled back by a supplied post-condition. A failed transaction is included in a block (mining fees are paid to the miner and are non-refundable), but failed because it violated the rules of the Stacks protocol or of the smart contract it interacted with. See the error code and/or the contract to learn more about the specific cause of failure.VM Error: Post-condition check failure on fungible asset SP3Y2ZSH8P7D50B0VBTSX11S7XSG24M1VB9YFQA4K.token-aeusdc::aeUSDC owned by SP3Y2ZSH8P7D50B0VBTSX11S7XSG24M1VB9YFQA4K.bridge: 4999000000 SentEq 0
ID | |
From | |
To | |
Timestamp | 2025-06-18 08:17:03 |
Timestamp 2025-06-18 08:17:03 | |
Fee | 0.003 STX/<$0.01 |
Fee 0.003 STX/<$0.01 | |
Nonce | 48 |
Nonce 48 | |
Block height | |
Block height | |
Block hash | |
Bitcoin Anchor | |
Bitcoin Anchor |
Deny mode
Only the post-conditions explicitly listed are allowed. Anything not listed will cause the transaction to fail.From | Condition | Asset/Amount | To |
|---|---|---|---|
| SPJG…868RN | Transfers exactly | 4999000000 aeUSDC |
Filter:
Contract log
STX lock
STX token
Fungible token
Non fungible token
View deployment
Loading...
This Stacks Explorer is built and maintained by Hiro
Market data provided by LunarCrush