Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96b59bb77e9fd1c251d06ce6ec7374527e9e623b0a5728b0f39cf637ea0604da

Tx prefix hash: 8ed7de8c9dd9dceffed66cae69097a4be6d92d9deb40fa8888940753899855d6
Tx public key: bf3c89b2899a43357a4a49b8a988b3e882b1f1643c30534e2db4092df9920eb7
Timestamp: 1759839981 Timestamp [UCT]: 2025-10-07 12:26:21 Age [y:d:h:m:s]: 00:045:12:04:45
Block: 1384729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32578 RingCT/type: yes/0
Extra: 01bf3c89b2899a43357a4a49b8a988b3e882b1f1643c30534e2db4092df9920eb7021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7244cd7448f22f4710d6d9c5b841d637129f3d50dfa2d66969164cc8a172cb16 0.600000000000 1872882 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": 1384739, "vin": [ { "gen": { "height": 1384729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7244cd7448f22f4710d6d9c5b841d637129f3d50dfa2d66969164cc8a172cb16" } } ], "extra": [ 1, 191, 60, 137, 178, 137, 154, 67, 53, 122, 74, 73, 184, 169, 136, 179, 232, 130, 177, 241, 100, 60, 48, 83, 78, 45, 180, 9, 45, 249, 146, 14, 183, 2, 17, 0, 0, 0, 3, 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