Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 239817fcf02cba2eb4b4e2f8a4653037795b4df922298d791256764eb1b73a00

Tx prefix hash: 231d982623f6ba44ae427a4242c38b940c69431df60dcbd3c7568a34ea560bb2
Tx public key: d18f1335d2da4f0a205e2651b0b47135b1b4bca30f6ba963bebe1378023db08c
Timestamp: 1752639529 Timestamp [UCT]: 2025-07-16 04:18:49 Age [y:d:h:m:s]: 00:119:16:46:24
Block: 1326469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84295 RingCT/type: yes/0
Extra: 01d18f1335d2da4f0a205e2651b0b47135b1b4bca30f6ba963bebe1378023db08c021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 740f5085de19706cb2e0cb820cb6e369d721b590f8c4492b7b9dd10c7d3b9dba 0.600000000000 1814220 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": 1326479, "vin": [ { "gen": { "height": 1326469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "740f5085de19706cb2e0cb820cb6e369d721b590f8c4492b7b9dd10c7d3b9dba" } } ], "extra": [ 1, 209, 143, 19, 53, 210, 218, 79, 10, 32, 94, 38, 81, 176, 180, 113, 53, 177, 180, 188, 163, 15, 107, 169, 99, 190, 190, 19, 120, 2, 61, 176, 140, 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