Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73482396f6fffb2bd53e809b431cff2de03559c40b48ab589eac35be0023c817

Tx prefix hash: d93b361677ff71308f74e540362359e8112896fc0abf8c6b00c023e00592ffab
Tx public key: a09e16e84667bb504ebab21c2b3c0bd519e7afcb94dbcbda5558d5ad4022f7a9
Timestamp: 1759311220 Timestamp [UCT]: 2025-10-01 09:33:40 Age [y:d:h:m:s]: 00:083:19:09:43
Block: 1380342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60008 RingCT/type: yes/0
Extra: 01a09e16e84667bb504ebab21c2b3c0bd519e7afcb94dbcbda5558d5ad4022f7a9021100000005d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8bd32d1fcb664d70596fb6d6e7bff0ac0d80218c3523fdfd083ab046f680be6 0.600000000000 1868453 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": 1380352, "vin": [ { "gen": { "height": 1380342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8bd32d1fcb664d70596fb6d6e7bff0ac0d80218c3523fdfd083ab046f680be6" } } ], "extra": [ 1, 160, 158, 22, 232, 70, 103, 187, 80, 78, 186, 178, 28, 43, 60, 11, 213, 25, 231, 175, 203, 148, 219, 203, 218, 85, 88, 213, 173, 64, 34, 247, 169, 2, 17, 0, 0, 0, 5, 216, 231, 210, 65, 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