Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da9900572a525844b46efb961f0c7da823fcdb06f32c3d6eacc48364017a1c9d

Tx prefix hash: 6d6abec1249b5d8cb733ad9c3ba030311acec1a578f1c1417ffca6b9b8eaf20c
Tx public key: d7796db45e02e026b717efe7ab6ccc99a28db3894985b811a84ef1f656fdb4b6
Timestamp: 1703357745 Timestamp [UCT]: 2023-12-23 18:55:45 Age [y:d:h:m:s]: 01:064:23:20:12
Block: 919581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307524 RingCT/type: yes/0
Extra: 01d7796db45e02e026b717efe7ab6ccc99a28db3894985b811a84ef1f656fdb4b60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f25e2ec11e2a957adffa6ce487c5e0dff23ab9ba16cf81d5999c39bebc46be26 0.600000000000 1377255 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": 919591, "vin": [ { "gen": { "height": 919581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f25e2ec11e2a957adffa6ce487c5e0dff23ab9ba16cf81d5999c39bebc46be26" } } ], "extra": [ 1, 215, 121, 109, 180, 94, 2, 224, 38, 183, 23, 239, 231, 171, 108, 204, 153, 162, 141, 179, 137, 73, 133, 184, 17, 168, 78, 241, 246, 86, 253, 180, 182, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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