Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db4e1de6ac1c5857ca4ea60b11006c1e7becaf3a95fb1ecce6959403104fab5c

Tx prefix hash: 9407711c3a1bd2b3700a56fd4a8c3f83cbb94e775781770045620ea67fdd0fd6
Tx public key: 84699947e9a3626bcb08236aef05fcfa92d8a5257b62321df057719e2c0ad217
Timestamp: 1750316332 Timestamp [UCT]: 2025-06-19 06:58:52 Age [y:d:h:m:s]: 00:155:02:36:05
Block: 1308178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108678 RingCT/type: yes/0
Extra: 0184699947e9a3626bcb08236aef05fcfa92d8a5257b62321df057719e2c0ad217021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4062590137b741cb769e2c0c086d4698b35e70e96697106449fcc13b0bbd92e 0.600000000000 1795791 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": 1308188, "vin": [ { "gen": { "height": 1308178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4062590137b741cb769e2c0c086d4698b35e70e96697106449fcc13b0bbd92e" } } ], "extra": [ 1, 132, 105, 153, 71, 233, 163, 98, 107, 203, 8, 35, 106, 239, 5, 252, 250, 146, 216, 165, 37, 123, 98, 50, 29, 240, 87, 113, 158, 44, 10, 210, 23, 2, 17, 0, 0, 0, 3, 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