Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9805dd451c80ae84a64c6dad9a8e8ca19e9d85d8bc5b5d25a053c9c7f521b25

Tx prefix hash: 944d82689a7964aaacaa14db40821d228719ce71dbf5e617f7a5435ae8e978dc
Tx public key: d64cc5e1e3ed4648968e6c3edd0a61a26e01e87b61d20ea3e9c9b63bf7577bbc
Timestamp: 1703353286 Timestamp [UCT]: 2023-12-23 17:41:26 Age [y:d:h:m:s]: 01:111:19:53:59
Block: 919544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341054 RingCT/type: yes/0
Extra: 01d64cc5e1e3ed4648968e6c3edd0a61a26e01e87b61d20ea3e9c9b63bf7577bbc0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cf57aa7749aea58ffe699855ae3e477145c68625f3c06dc70bf74263681b05f 0.600000000000 1377218 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": 919554, "vin": [ { "gen": { "height": 919544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cf57aa7749aea58ffe699855ae3e477145c68625f3c06dc70bf74263681b05f" } } ], "extra": [ 1, 214, 76, 197, 225, 227, 237, 70, 72, 150, 142, 108, 62, 221, 10, 97, 162, 110, 1, 232, 123, 97, 210, 14, 163, 233, 201, 182, 59, 247, 87, 123, 188, 2, 17, 0, 0, 0, 6, 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