Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7021e34bb63c64b0f8be3f67cd1ef8ba9dbbcf4c3367d7e46898ac0ab9b73663

Tx prefix hash: 21c3cc106da04f068a3098ffbd7b3b3d1a2685e160bcb23ea7b3d417ce93ffe4
Tx public key: 0ce8df7b593bd673c8d22ce01b2c7a000fab1b09a7898191a3f1fe7e9ae92dc7
Timestamp: 1714339286 Timestamp [UCT]: 2024-04-28 21:21:26 Age [y:d:h:m:s]: 00:256:16:18:01
Block: 1010620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183724 RingCT/type: yes/0
Extra: 010ce8df7b593bd673c8d22ce01b2c7a000fab1b09a7898191a3f1fe7e9ae92dc70211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a47ea1fb51972d5f1618220e628baa445abe389ae034c6539a164215b481287 0.600000000000 1472626 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": 1010630, "vin": [ { "gen": { "height": 1010620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a47ea1fb51972d5f1618220e628baa445abe389ae034c6539a164215b481287" } } ], "extra": [ 1, 12, 232, 223, 123, 89, 59, 214, 115, 200, 210, 44, 224, 27, 44, 122, 0, 15, 171, 27, 9, 167, 137, 129, 145, 163, 241, 254, 126, 154, 233, 45, 199, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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