Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb2d3dd7ffc2936bf54237e1a701f84cf991fb296309605b04b13eb70e08cf38

Tx prefix hash: ef6aef7c4136ea9ef3df5a14b89292bb37b1278bffbd4018095b7fa96b6dea1a
Tx public key: 9dfad74373ad71e325176402b7528cd1d766b3a92d55dc1db74d41b22c0d1b12
Timestamp: 1763728983 Timestamp [UCT]: 2025-11-21 12:43:03 Age [y:d:h:m:s]: 00:043:01:02:43
Block: 1416951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30837 RingCT/type: yes/0
Extra: 019dfad74373ad71e325176402b7528cd1d766b3a92d55dc1db74d41b22c0d1b1202110000000670609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b80c19be39d0b4a283487c095a81da5f42781d2f9932bebd91d4f97b571109a1 0.600000000000 1905472 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": 1416961, "vin": [ { "gen": { "height": 1416951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b80c19be39d0b4a283487c095a81da5f42781d2f9932bebd91d4f97b571109a1" } } ], "extra": [ 1, 157, 250, 215, 67, 115, 173, 113, 227, 37, 23, 100, 2, 183, 82, 140, 209, 215, 102, 179, 169, 45, 85, 220, 29, 183, 77, 65, 178, 44, 13, 27, 18, 2, 17, 0, 0, 0, 6, 112, 96, 157, 3, 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