Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16a0cfc4f4b969a6342be7f39736517a0db1c5f494fc40a33ca80370d7c896f

Tx prefix hash: 0cf6d5aa3ab72677095e1ce35fce4ae73f5fbf65879edd78f2a6c794ba6fa191
Tx public key: 1a1babb17264db94240425ce40192386dd80d7ea8203a70b7627f275df3a0882
Timestamp: 1751461304 Timestamp [UCT]: 2025-07-02 13:01:44 Age [y:d:h:m:s]: 00:188:08:44:12
Block: 1317242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132929 RingCT/type: yes/0
Extra: 011a1babb17264db94240425ce40192386dd80d7ea8203a70b7627f275df3a0882021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 209f78f2c8e62b44da2ee2b8b199a8f30c136e34d9beaeaae6c07dda36568e8f 0.600000000000 1804909 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": 1317252, "vin": [ { "gen": { "height": 1317242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "209f78f2c8e62b44da2ee2b8b199a8f30c136e34d9beaeaae6c07dda36568e8f" } } ], "extra": [ 1, 26, 27, 171, 177, 114, 100, 219, 148, 36, 4, 37, 206, 64, 25, 35, 134, 221, 128, 215, 234, 130, 3, 167, 11, 118, 39, 242, 117, 223, 58, 8, 130, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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