Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c58d188ee2d7928977bcc9a2ecb1552e0e1cadf059bc0450e5d895da8ae6160

Tx prefix hash: 331b7b7d9dd6fa343de369576a03d25fca5d4ecf1f155ba76e655dc478b26f6b
Tx public key: 13f7c811256e6c2e3e35ff80bd9a457dc0198792b15d2349e19a38114991c518
Timestamp: 1712583666 Timestamp [UCT]: 2024-04-08 13:41:06 Age [y:d:h:m:s]: 00:220:20:33:07
Block: 996045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158135 RingCT/type: yes/0
Extra: 0113f7c811256e6c2e3e35ff80bd9a457dc0198792b15d2349e19a38114991c51802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29ce0ac2fe9975c06d4ecdb3c18783c838694d5ac718a81d335f42547f7813c5 0.600000000000 1456461 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": 996055, "vin": [ { "gen": { "height": 996045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29ce0ac2fe9975c06d4ecdb3c18783c838694d5ac718a81d335f42547f7813c5" } } ], "extra": [ 1, 19, 247, 200, 17, 37, 110, 108, 46, 62, 53, 255, 128, 189, 154, 69, 125, 192, 25, 135, 146, 177, 93, 35, 73, 225, 154, 56, 17, 73, 145, 197, 24, 2, 17, 0, 0, 0, 1, 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