Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 601df584a4941056c9eee0eb907966aa1fdad3fb3159a8f12c0efaac5344434a

Tx prefix hash: 68652330b38fd19102f2fdf3f1b8e9096b37343dd6383d914577b7f3796822ee
Tx public key: d79783610415ea35d63dbe73c4ca65c2a955b601c8d6b16f4ee62b545a401ffb
Timestamp: 1741671587 Timestamp [UCT]: 2025-03-11 05:39:47 Age [y:d:h:m:s]: 00:253:03:58:29
Block: 1236767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178665 RingCT/type: yes/0
Extra: 01d79783610415ea35d63dbe73c4ca65c2a955b601c8d6b16f4ee62b545a401ffb02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1c679184c2da5dd614d680f29609e147467748a40d9b29634179bb43ae8d803 0.600000000000 1723720 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": 1236777, "vin": [ { "gen": { "height": 1236767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1c679184c2da5dd614d680f29609e147467748a40d9b29634179bb43ae8d803" } } ], "extra": [ 1, 215, 151, 131, 97, 4, 21, 234, 53, 214, 61, 190, 115, 196, 202, 101, 194, 169, 85, 182, 1, 200, 214, 177, 111, 78, 230, 43, 84, 90, 64, 31, 251, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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