Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 155df901365d49e2e420e4efa3de5366a051c00abf211595b6e43d9e703e01a7

Tx prefix hash: baef472e8964d476319bb967db3a326d3c05c86dcdf3abde6cf5d450fc5b1fb8
Tx public key: 0f67bfa58002243f41249a777b647b436dce4371e0d9328041047aaf7bda4ceb
Timestamp: 1710721204 Timestamp [UCT]: 2024-03-18 00:20:04 Age [y:d:h:m:s]: 01:051:15:15:54
Block: 980650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297880 RingCT/type: yes/0
Extra: 010f67bfa58002243f41249a777b647b436dce4371e0d9328041047aaf7bda4ceb02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a13a9d1cc9fea3b6bb26c2b69b94c96be87e1d1dc46cbaca1051271cab90806d 0.600000000000 1440731 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": 980660, "vin": [ { "gen": { "height": 980650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a13a9d1cc9fea3b6bb26c2b69b94c96be87e1d1dc46cbaca1051271cab90806d" } } ], "extra": [ 1, 15, 103, 191, 165, 128, 2, 36, 63, 65, 36, 154, 119, 123, 100, 123, 67, 109, 206, 67, 113, 224, 217, 50, 128, 65, 4, 122, 175, 123, 218, 76, 235, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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