Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc304f4b001583d3c1c7bf369e6c8dff6d66412d6a57f64b4b19fc9e666324fd

Tx prefix hash: 38840b0524fe28a56495e330c7053681ba8a58512de840ccbe56d2b8a86a22bf
Tx public key: c85bd2e3f0404f254596582cd280a226cd0ac14275e1d45e3c2f47eb54351a77
Timestamp: 1737979276 Timestamp [UCT]: 2025-01-27 12:01:16 Age [y:d:h:m:s]: 00:328:13:41:07
Block: 1206225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232612 RingCT/type: yes/0
Extra: 01c85bd2e3f0404f254596582cd280a226cd0ac14275e1d45e3c2f47eb54351a770211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f5b1fd58b000971b619cf18cfb54addaae73ba9c86ff671bd5b28cbb4c917a3 0.600000000000 1692928 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": 1206235, "vin": [ { "gen": { "height": 1206225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f5b1fd58b000971b619cf18cfb54addaae73ba9c86ff671bd5b28cbb4c917a3" } } ], "extra": [ 1, 200, 91, 210, 227, 240, 64, 79, 37, 69, 150, 88, 44, 210, 128, 162, 38, 205, 10, 193, 66, 117, 225, 212, 94, 60, 47, 71, 235, 84, 53, 26, 119, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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