Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b0059e42613faaab5b29092cbfdcf8c4951ec7dfdac103c2eedb2c9433c534a

Tx prefix hash: afe7e7832f6060ef87da21353da9226c3272ac0b503d27aa840b352502223c67
Tx public key: abe6f382a28020fe282d958a2d2dc3e8ed6afa7afa7a76ef81f372ecb88d815d
Timestamp: 1754788478 Timestamp [UCT]: 2025-08-10 01:14:38 Age [y:d:h:m:s]: 00:011:17:44:00
Block: 1343824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7631 RingCT/type: yes/0
Extra: 01abe6f382a28020fe282d958a2d2dc3e8ed6afa7afa7a76ef81f372ecb88d815d021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55e846326eb5f6375108a16fd3b3d9e375dc47d29148047a26dc96f176658fb8 0.600000000000 1831667 of 15

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": 1343834, "vin": [ { "gen": { "height": 1343824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55e846326eb5f6375108a16fd3b3d9e375dc47d29148047a26dc96f176658fb8" } } ], "extra": [ 1, 171, 230, 243, 130, 162, 128, 32, 254, 40, 45, 149, 138, 45, 45, 195, 232, 237, 106, 250, 122, 250, 122, 118, 239, 129, 243, 114, 236, 184, 141, 129, 93, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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