Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8ba1802977150fb3795158a15e2e1cf14b35eef45f70b4e42f2b72c560d798d

Tx prefix hash: b3f650bcd35e2641570d8a9fe7c43599dd33deee5a4552b01199f9fc80b826b8
Tx public key: a050de5dac2a871fdf0dff08f6009b658b947c3d71479d6dafe9996d4ff85328
Timestamp: 1764871308 Timestamp [UCT]: 2025-12-04 18:01:48 Age [y:d:h:m:s]: 00:029:16:20:17
Block: 1426440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21252 RingCT/type: yes/0
Extra: 01a050de5dac2a871fdf0dff08f6009b658b947c3d71479d6dafe9996d4ff85328021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d50b13fda65e70a29e101d8ea7052f4e55cf57745dfaabbd4781dbd43b766e60 0.600000000000 1915131 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": 1426450, "vin": [ { "gen": { "height": 1426440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d50b13fda65e70a29e101d8ea7052f4e55cf57745dfaabbd4781dbd43b766e60" } } ], "extra": [ 1, 160, 80, 222, 93, 172, 42, 135, 31, 223, 13, 255, 8, 246, 0, 155, 101, 139, 148, 124, 61, 113, 71, 157, 109, 175, 233, 153, 109, 79, 248, 83, 40, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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