Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cdaf72f7b42566ab5b54f8cda9db8984849018af3877f7fdfb9f51aee010d55

Tx prefix hash: 8f4befdc3fd1d446330eab0ce782ea77c88e24b99e32726bb376d2c277311a23
Tx public key: 45dc32d352669fcc73a38dc61b6250546fff265e7337d3a34f33bddf5f36f9ce
Timestamp: 1750414910 Timestamp [UCT]: 2025-06-20 10:21:50 Age [y:d:h:m:s]: 00:199:13:31:20
Block: 1308977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140557 RingCT/type: yes/0
Extra: 0145dc32d352669fcc73a38dc61b6250546fff265e7337d3a34f33bddf5f36f9ce021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca700cf2e695b449888c8d35f1b1f7e68436cff0515860b2370a9c7e1ba6c475 0.600000000000 1796592 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": 1308987, "vin": [ { "gen": { "height": 1308977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca700cf2e695b449888c8d35f1b1f7e68436cff0515860b2370a9c7e1ba6c475" } } ], "extra": [ 1, 69, 220, 50, 211, 82, 102, 159, 204, 115, 163, 141, 198, 27, 98, 80, 84, 111, 255, 38, 94, 115, 55, 211, 163, 79, 51, 189, 223, 95, 54, 249, 206, 2, 17, 0, 0, 0, 2, 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