Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c7904f8d1b695435853d149d1d6900b36249f6373f1212d9aeb7654f28c180

Tx prefix hash: 586d1929290662a10827060e4aeff7d9a64ffe4a1821bccf55b57cf23f175c04
Tx public key: 280d98772a2dae97cb69733ea777ea6e73551dde8fd1d8836a1d692c3c22d0f9
Timestamp: 1745767207 Timestamp [UCT]: 2025-04-27 15:20:07 Age [y:d:h:m:s]: 00:207:11:49:46
Block: 1270669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145993 RingCT/type: yes/0
Extra: 01280d98772a2dae97cb69733ea777ea6e73551dde8fd1d8836a1d692c3c22d0f90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc188a513b5da8e7c5474676dd0ae9cc8edda578f1db31c497efb4f5b4a57bfd 0.600000000000 1757914 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": 1270679, "vin": [ { "gen": { "height": 1270669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc188a513b5da8e7c5474676dd0ae9cc8edda578f1db31c497efb4f5b4a57bfd" } } ], "extra": [ 1, 40, 13, 152, 119, 42, 45, 174, 151, 203, 105, 115, 62, 167, 119, 234, 110, 115, 85, 29, 222, 143, 209, 216, 131, 106, 29, 105, 44, 60, 34, 208, 249, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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