Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac3477bedf5dd67e5626d7166c8c212924a4315eef22d7ec9f7fdcfd218b51db

Tx prefix hash: 84a1dbff36a83d573b3bf3cf1dc12b0dd3e81da90d098dad51c4b6b26ba4dd5e
Tx public key: 60dc6ae14d234b9542d3af8f84fed9917d01ab4e4cde2334333d69a91853628b
Timestamp: 1752894944 Timestamp [UCT]: 2025-07-19 03:15:44 Age [y:d:h:m:s]: 00:160:18:08:27
Block: 1328549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113734 RingCT/type: yes/0
Extra: 0160dc6ae14d234b9542d3af8f84fed9917d01ab4e4cde2334333d69a91853628b021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb1ab4bf4cca8dba22a86db9de6ce545feda2d73961e1079fe923cf9a49112cf 0.600000000000 1816312 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": 1328559, "vin": [ { "gen": { "height": 1328549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb1ab4bf4cca8dba22a86db9de6ce545feda2d73961e1079fe923cf9a49112cf" } } ], "extra": [ 1, 96, 220, 106, 225, 77, 35, 75, 149, 66, 211, 175, 143, 132, 254, 217, 145, 125, 1, 171, 78, 76, 222, 35, 52, 51, 61, 105, 169, 24, 83, 98, 139, 2, 17, 0, 0, 0, 1, 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