Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d5460afc225b7b522da48bb017346daf22f5ee1a1037d674c8943b817689b12

Tx prefix hash: 5952a7afc078f54ea7c4b8436594aee83d17a8843a346fb051fd9f60252ba8f4
Tx public key: b5e6a9e8a0e6adeebff8aa10bc2f3fd0e8b697f6d2a17290aaca0eec2fd67c91
Timestamp: 1751074474 Timestamp [UCT]: 2025-06-28 01:34:34 Age [y:d:h:m:s]: 00:146:15:45:12
Block: 1314197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102893 RingCT/type: yes/0
Extra: 01b5e6a9e8a0e6adeebff8aa10bc2f3fd0e8b697f6d2a17290aaca0eec2fd67c91021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f4ed54a8367be547648d3e02798dd876ec57e005d1082782804a6e7dd959b52 0.600000000000 1801842 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": 1314207, "vin": [ { "gen": { "height": 1314197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f4ed54a8367be547648d3e02798dd876ec57e005d1082782804a6e7dd959b52" } } ], "extra": [ 1, 181, 230, 169, 232, 160, 230, 173, 238, 191, 248, 170, 16, 188, 47, 63, 208, 232, 182, 151, 246, 210, 161, 114, 144, 170, 202, 14, 236, 47, 214, 124, 145, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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