Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 04ebf01e8268bfb1cdc9f729f1ce0c8e9b39a82f754595eedf005f805859b3cf

Tx prefix hash: 6fa053a62c5777fd03daf370c2dead634bb8b8d3aa198066d5eb848c044b973f
Tx public key: 6fb0aa20a711275ba2c62c7a218b475fa0100d95edd63e754f6fb19f19407fdb
Timestamp: 1659112738 Timestamp [UCT]: 2022-07-29 16:38:58 Age [y:d:h:m:s]: 02:250:03:17:30
Block: 554375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 699963 RingCT/type: yes/0
Extra: 016fb0aa20a711275ba2c62c7a218b475fa0100d95edd63e754f6fb19f19407fdb0211000000186570b1ef000000000000000000

1 output(s) for total of 8.935639080000 dcy

stealth address amount amount idx
00: 401dc4363fa72103feda36198031d1dd844d0240cd353e5dc54329292725ffd4 8.935639080000 986225 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 554385, "vin": [ { "gen": { "height": 554375 } } ], "vout": [ { "amount": 8935639080, "target": { "key": "401dc4363fa72103feda36198031d1dd844d0240cd353e5dc54329292725ffd4" } } ], "extra": [ 1, 111, 176, 170, 32, 167, 17, 39, 91, 162, 198, 44, 122, 33, 139, 71, 95, 160, 16, 13, 149, 237, 214, 62, 117, 79, 111, 177, 159, 25, 64, 127, 219, 2, 17, 0, 0, 0, 24, 101, 112, 177, 239, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8