Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a3cd6c973fa4d1e086e01e4e3f3fb64392108e8fc7e20dc876baba2625209cb

Tx prefix hash: 923902bd892de947703232a57d3fc2e174877b1e673ed73a54c80c4a15e25c3a
Tx public key: f9dabe0f10531f879da395d4f6b7aec7aecdf2ad8dc064da89bc3f9ff1178f60
Timestamp: 1761843305 Timestamp [UCT]: 2025-10-30 16:55:05 Age [y:d:h:m:s]: 00:007:05:21:34
Block: 1401343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5162 RingCT/type: yes/0
Extra: 01f9dabe0f10531f879da395d4f6b7aec7aecdf2ad8dc064da89bc3f9ff1178f60021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6724a0394a85345771f269cf5286f4c9b5a700c7502884a34579ffc873cde0e 0.600000000000 1889662 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": 1401353, "vin": [ { "gen": { "height": 1401343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6724a0394a85345771f269cf5286f4c9b5a700c7502884a34579ffc873cde0e" } } ], "extra": [ 1, 249, 218, 190, 15, 16, 83, 31, 135, 157, 163, 149, 212, 246, 183, 174, 199, 174, 205, 242, 173, 141, 192, 100, 218, 137, 188, 63, 159, 241, 23, 143, 96, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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