Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8fd63d81e0a84154de02aaad5bbf58215e3ee2a89e40da34118a9d2521da40d

Tx prefix hash: 10c7d6f40037c2bf64f0baeab5ba7b319f4e9fd912cbb9bf657c324d089c4cc6
Tx public key: 626ccb7c991d5643caa8b338e256ceca45640881443edb454fc8d81037c35210
Timestamp: 1694038234 Timestamp [UCT]: 2023-09-06 22:10:34 Age [y:d:h:m:s]: 01:207:14:00:33
Block: 842507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409452 RingCT/type: yes/0
Extra: 01626ccb7c991d5643caa8b338e256ceca45640881443edb454fc8d81037c352100211000000074b8f5122000000000000000000

1 output(s) for total of 0.991831213000 dcy

stealth address amount amount idx
00: e80cbc76209b028677d36bbb4ba943b5dda2ad511d5b83a31d7da405d80438d4 0.991831213000 1295633 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": 842517, "vin": [ { "gen": { "height": 842507 } } ], "vout": [ { "amount": 991831213, "target": { "key": "e80cbc76209b028677d36bbb4ba943b5dda2ad511d5b83a31d7da405d80438d4" } } ], "extra": [ 1, 98, 108, 203, 124, 153, 29, 86, 67, 202, 168, 179, 56, 226, 86, 206, 202, 69, 100, 8, 129, 68, 62, 219, 69, 79, 200, 216, 16, 55, 195, 82, 16, 2, 17, 0, 0, 0, 7, 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