Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a32a5be916c67dfc87fa89660dcd65cce69dc0a4c5f1e67766d75b0d48dbdc98

Tx prefix hash: db9ddba5343bbdbb6bddc18177898a8b681134aa75a39f85b405a3f11d318a4f
Tx public key: 0fb2b2ac9474cf0e79593d4c0f455a36072aec7bf6324ea229e18d3943155eda
Timestamp: 1750242078 Timestamp [UCT]: 2025-06-18 10:21:18 Age [y:d:h:m:s]: 00:155:15:24:06
Block: 1307588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109033 RingCT/type: yes/0
Extra: 010fb2b2ac9474cf0e79593d4c0f455a36072aec7bf6324ea229e18d3943155eda02110000000abf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7246ccd060a5252b839b66a7e1489317992c0485f52f0ec499fde4e3221916d 0.600000000000 1795199 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": 1307598, "vin": [ { "gen": { "height": 1307588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7246ccd060a5252b839b66a7e1489317992c0485f52f0ec499fde4e3221916d" } } ], "extra": [ 1, 15, 178, 178, 172, 148, 116, 207, 14, 121, 89, 61, 76, 15, 69, 90, 54, 7, 42, 236, 123, 246, 50, 78, 162, 41, 225, 141, 57, 67, 21, 94, 218, 2, 17, 0, 0, 0, 10, 191, 81, 178, 162, 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