Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ead0a4708391896a3417af3f26bd765fc10bc525ca4c5a2fdb0eb9789efa4ba2

Tx prefix hash: cf46d87e203209569649e0c7123b64e4b2d9c3e6fb6342a04884d876b402d197
Tx public key: eec26614e896b6c7e9d63e1e408891231b1c358baf205b63b9cb9e268f2c0400
Timestamp: 1689688091 Timestamp [UCT]: 2023-07-18 13:48:11 Age [y:d:h:m:s]: 01:226:20:50:35
Block: 806532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423209 RingCT/type: yes/0
Extra: 01eec26614e896b6c7e9d63e1e408891231b1c358baf205b63b9cb9e268f2c040002110000000c4b8f5122000000000000000000

1 output(s) for total of 1.305042926000 dcy

stealth address amount amount idx
00: 9baa3699dc38974d4b8ef199870c66527ed26280df244d244f1823387be3dd7c 1.305042926000 1257958 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": 806542, "vin": [ { "gen": { "height": 806532 } } ], "vout": [ { "amount": 1305042926, "target": { "key": "9baa3699dc38974d4b8ef199870c66527ed26280df244d244f1823387be3dd7c" } } ], "extra": [ 1, 238, 194, 102, 20, 232, 150, 182, 199, 233, 214, 62, 30, 64, 136, 145, 35, 27, 28, 53, 139, 175, 32, 91, 99, 185, 203, 158, 38, 143, 44, 4, 0, 2, 17, 0, 0, 0, 12, 75, 143, 81, 34, 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