Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97e10e6c506922edd2df4d74833dde3a26423147000d8c172ae07f308428d211

Tx prefix hash: ab4b2ba848d568099d311be9de060100c816e57552e4d37a199a8f325f674447
Tx public key: f9b4541f5e4e391b27f77d8348ffb959bfeef7cc9ae37b5fcac1cc39334e8c9f
Timestamp: 1755123971 Timestamp [UCT]: 2025-08-13 22:26:11 Age [y:d:h:m:s]: 00:092:07:41:19
Block: 1346309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65446 RingCT/type: yes/0
Extra: 01f9b4541f5e4e391b27f77d8348ffb959bfeef7cc9ae37b5fcac1cc39334e8c9f021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808daae863217b029713bcb3fa88906fec5e241a6cc39acb7875d9e68692c96e 0.600000000000 1834208 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": 1346319, "vin": [ { "gen": { "height": 1346309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808daae863217b029713bcb3fa88906fec5e241a6cc39acb7875d9e68692c96e" } } ], "extra": [ 1, 249, 180, 84, 31, 94, 78, 57, 27, 39, 247, 125, 131, 72, 255, 185, 89, 191, 238, 247, 204, 154, 227, 123, 95, 202, 193, 204, 57, 51, 78, 140, 159, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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