Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a39024e722e1fa7675acf922c83326e4b52e36fb50040918e206e5d3bd843b89

Tx prefix hash: f0863780ef1e98b59d34236eae415efb1aa92e5a6e5d358d3a121f5544640fe0
Tx public key: 6d9e5e95de197178f39ef19ffe76ba4610a803adf5ec9c337401a4080ff7ddbc
Timestamp: 1714996796 Timestamp [UCT]: 2024-05-06 11:59:56 Age [y:d:h:m:s]: 00:336:03:16:41
Block: 1016072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240278 RingCT/type: yes/0
Extra: 016d9e5e95de197178f39ef19ffe76ba4610a803adf5ec9c337401a4080ff7ddbc0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 050a633644dda4384edc9bbd2d8c238b14c6442a0f59c7d428e52c1e66bf0f2e 0.600000000000 1479555 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": 1016082, "vin": [ { "gen": { "height": 1016072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "050a633644dda4384edc9bbd2d8c238b14c6442a0f59c7d428e52c1e66bf0f2e" } } ], "extra": [ 1, 109, 158, 94, 149, 222, 25, 113, 120, 243, 158, 241, 159, 254, 118, 186, 70, 16, 168, 3, 173, 245, 236, 156, 51, 116, 1, 164, 8, 15, 247, 221, 188, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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