Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c53f6163a0cee0ed27d93eb6d01f98a8206df785c67ed33329bdbd1bbd6e0b65

Tx prefix hash: 658b9cbe2341669ce6301b37697178939af5c41d91fe824f9747bec7eaa9c141
Tx public key: a0ac3dd7ec23197318e79bb1dd88e501e61942f0a5f3973f083c77679ae3de70
Timestamp: 1696997246 Timestamp [UCT]: 2023-10-11 04:07:26 Age [y:d:h:m:s]: 01:202:16:15:26
Block: 867057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405891 RingCT/type: yes/0
Extra: 01a0ac3dd7ec23197318e79bb1dd88e501e61942f0a5f3973f083c77679ae3de70021100000002faf35c9c000000000000000000

1 output(s) for total of 0.822394615000 dcy

stealth address amount amount idx
00: b69128292899dee0272df3bdd4febaf591582efd522e70fa73bf26d4541c4159 0.822394615000 1321709 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": 867067, "vin": [ { "gen": { "height": 867057 } } ], "vout": [ { "amount": 822394615, "target": { "key": "b69128292899dee0272df3bdd4febaf591582efd522e70fa73bf26d4541c4159" } } ], "extra": [ 1, 160, 172, 61, 215, 236, 35, 25, 115, 24, 231, 155, 177, 221, 136, 229, 1, 230, 25, 66, 240, 165, 243, 151, 63, 8, 60, 119, 103, 154, 227, 222, 112, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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