Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53802a4c065b6380bf80127cf7cab4d09fe56fe3a91dc7ae17e2ebdb7e8fd39e

Tx prefix hash: e65897bdb5d888d176185e98d909be1ae82f7c289c8a5728a5ee3ba09bde9dfb
Tx public key: bb66b2201eae5b856803b2ef8e6db670734100f7bf17ff008d193ab78a527b94
Timestamp: 1753553130 Timestamp [UCT]: 2025-07-26 18:05:30 Age [y:d:h:m:s]: 00:153:06:45:30
Block: 1333961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108419 RingCT/type: yes/0
Extra: 01bb66b2201eae5b856803b2ef8e6db670734100f7bf17ff008d193ab78a527b94021100000001db6acbd3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 139efb28ea70296f4797332fea827c99c34b982f9f2db3dab07717fcd45969b0 0.600000000000 1821760 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": 1333971, "vin": [ { "gen": { "height": 1333961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "139efb28ea70296f4797332fea827c99c34b982f9f2db3dab07717fcd45969b0" } } ], "extra": [ 1, 187, 102, 178, 32, 30, 174, 91, 133, 104, 3, 178, 239, 142, 109, 182, 112, 115, 65, 0, 247, 191, 23, 255, 0, 141, 25, 58, 183, 138, 82, 123, 148, 2, 17, 0, 0, 0, 1, 219, 106, 203, 211, 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