Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a8ffc60af04c355175c73b3b9a61bbe768acf018c285a0ca2bd02328fcc2f2e

Tx prefix hash: a664a96be0e28faf556d21b24c55f77f950d21afa429d21b2417edf1a5437192
Tx public key: eb20690d26473b4b2229f47a900ffb8a273b31c1f26b3cd1fea0e8987a0d8911
Timestamp: 1762952234 Timestamp [UCT]: 2025-11-12 12:57:14 Age [y:d:h:m:s]: 00:041:12:58:52
Block: 1410529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29733 RingCT/type: yes/0
Extra: 01eb20690d26473b4b2229f47a900ffb8a273b31c1f26b3cd1fea0e8987a0d891102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1801752a97a9c5f2f6a1e5ff3dcb760f07677144ee37b117b6f597605f1a54bd 0.600000000000 1898982 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": 1410539, "vin": [ { "gen": { "height": 1410529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1801752a97a9c5f2f6a1e5ff3dcb760f07677144ee37b117b6f597605f1a54bd" } } ], "extra": [ 1, 235, 32, 105, 13, 38, 71, 59, 75, 34, 41, 244, 122, 144, 15, 251, 138, 39, 59, 49, 193, 242, 107, 60, 209, 254, 160, 232, 152, 122, 13, 137, 17, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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