Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59e4d80c2cf5566d7eb2819f90fac494c7ef9fdee637bd2182d727719c140546

Tx prefix hash: 224a6e692268d04ad83e7096005054e0944cd27688afefe2241a1fb1e585ca2c
Tx public key: eb7e620b0c82d663c62558d98b9e5d82d14ae2a3caa5a7c12e2692df1a955432
Timestamp: 1696904072 Timestamp [UCT]: 2023-10-10 02:14:32 Age [y:d:h:m:s]: 01:233:01:51:32
Block: 866285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427657 RingCT/type: yes/0
Extra: 01eb7e620b0c82d663c62558d98b9e5d82d14ae2a3caa5a7c12e2692df1a95543202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.827252743000 dcy

stealth address amount amount idx
00: 14590fb3bf99be624d3fe8d0450e5ad7aacfde17e39459aa467649e7716cf650 0.827252743000 1320865 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": 866295, "vin": [ { "gen": { "height": 866285 } } ], "vout": [ { "amount": 827252743, "target": { "key": "14590fb3bf99be624d3fe8d0450e5ad7aacfde17e39459aa467649e7716cf650" } } ], "extra": [ 1, 235, 126, 98, 11, 12, 130, 214, 99, 198, 37, 88, 217, 139, 158, 93, 130, 209, 74, 226, 163, 202, 165, 167, 193, 46, 38, 146, 223, 26, 149, 84, 50, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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