Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02a2a1d0a78bd5cab6962a39b188fde8ea3d3b580ea1267fd3c95f3c9ede74f7

Tx prefix hash: e744047b39a7d01c4a67e386e45477ccdf9d8d194980066e6d73d8974218617c
Tx public key: e6d86437fe5ed52399c4bfcf895dd38a959cbbd78d98158d10ec5cc42c8f3112
Timestamp: 1617113287 Timestamp [UCT]: 2021-03-30 14:08:07 Age [y:d:h:m:s]: 03:284:08:15:27
Block: 229750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 962707 RingCT/type: yes/0
Extra: 01e6d86437fe5ed52399c4bfcf895dd38a959cbbd78d98158d10ec5cc42c8f311202110000000d9c1fbdcc000000000000000000

1 output(s) for total of 106.356310466000 dcy

stealth address amount amount idx
00: dbabf1e486b328302931abb535b364b7a0b171bf09920ade835fef8194015100 106.356310466000 476786 of 0

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": 229760, "vin": [ { "gen": { "height": 229750 } } ], "vout": [ { "amount": 106356310466, "target": { "key": "dbabf1e486b328302931abb535b364b7a0b171bf09920ade835fef8194015100" } } ], "extra": [ 1, 230, 216, 100, 55, 254, 94, 213, 35, 153, 196, 191, 207, 137, 93, 211, 138, 149, 156, 187, 215, 141, 152, 21, 141, 16, 236, 92, 196, 44, 143, 49, 18, 2, 17, 0, 0, 0, 13, 156, 31, 189, 204, 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