Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624b1b717574df573483934fafba8fe96c081086a9e83cf9a27faa846c5f5225

Tx prefix hash: f978c68ff65c702bdbd54293c49ecb54576a10a978b8eab3c92ac931d3f46a23
Tx public key: e7d497a75389f4ceff7667bf25bf53cc2f41d8a19e001d1dfb8f82faed1b8838
Timestamp: 1673109667 Timestamp [UCT]: 2023-01-07 16:41:07 Age [y:d:h:m:s]: 02:098:23:00:34
Block: 669665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592422 RingCT/type: yes/0
Extra: 01e7d497a75389f4ceff7667bf25bf53cc2f41d8a19e001d1dfb8f82faed1b883802110000000152542ceb000000000000000000

1 output(s) for total of 3.707847140000 dcy

stealth address amount amount idx
00: 542ddf142e99d1aa3ba498f8a5748ca619993229e4f82df7aa092334a0fab48d 3.707847140000 1111016 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": 669675, "vin": [ { "gen": { "height": 669665 } } ], "vout": [ { "amount": 3707847140, "target": { "key": "542ddf142e99d1aa3ba498f8a5748ca619993229e4f82df7aa092334a0fab48d" } } ], "extra": [ 1, 231, 212, 151, 167, 83, 137, 244, 206, 255, 118, 103, 191, 37, 191, 83, 204, 47, 65, 216, 161, 158, 0, 29, 29, 251, 143, 130, 250, 237, 27, 136, 56, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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