Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9159e44779cb2ff33523b900d4db8aae67a9f7215e14a53e47d75943324d4c66

Tx prefix hash: 3762af6996df34cf8c0df3a9f7ad0a3b1397aa51cb4c96d6795e96716018b815
Tx public key: b748275911bf95f7b9ea76e5079cbec3da0fee5620128a81578006a1d73976cf
Timestamp: 1752545660 Timestamp [UCT]: 2025-07-15 02:14:20 Age [y:d:h:m:s]: 00:122:07:59:47
Block: 1325717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86162 RingCT/type: yes/0
Extra: 01b748275911bf95f7b9ea76e5079cbec3da0fee5620128a81578006a1d73976cf021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1c606a62b8f1ef651ae258d9a8e4c7490cc6bd47cba6893151f5d3dcf3f0a27 0.600000000000 1813464 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": 1325727, "vin": [ { "gen": { "height": 1325717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1c606a62b8f1ef651ae258d9a8e4c7490cc6bd47cba6893151f5d3dcf3f0a27" } } ], "extra": [ 1, 183, 72, 39, 89, 17, 191, 149, 247, 185, 234, 118, 229, 7, 156, 190, 195, 218, 15, 238, 86, 32, 18, 138, 129, 87, 128, 6, 161, 215, 57, 118, 207, 2, 17, 0, 0, 0, 1, 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