Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 826674e59037f1afd23ffb260e9f1cd60d02b0cd172ebee84b23d12aa527f70c

Tx prefix hash: 04d5dd7c7f2f64fbe90cf7c1e800f354961269ce159532e20e95da5b04816d8b
Tx public key: 0248799e7b38ad42be865f772f48e01097c334179fb213a1fa287f4a8c7cef71
Timestamp: 1699625552 Timestamp [UCT]: 2023-11-10 14:12:32 Age [y:d:h:m:s]: 01:153:21:18:07
Block: 888646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371172 RingCT/type: yes/0
Extra: 010248799e7b38ad42be865f772f48e01097c334179fb213a1fa287f4a8c7cef710211000000024b8f5122000000000000000000

1 output(s) for total of 0.697544329000 dcy

stealth address amount amount idx
00: 853fa438ffac2713aa087ad550ab61c1be3dcf1a4aac8731edc4fe72beb2228a 0.697544329000 1344599 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": 888656, "vin": [ { "gen": { "height": 888646 } } ], "vout": [ { "amount": 697544329, "target": { "key": "853fa438ffac2713aa087ad550ab61c1be3dcf1a4aac8731edc4fe72beb2228a" } } ], "extra": [ 1, 2, 72, 121, 158, 123, 56, 173, 66, 190, 134, 95, 119, 47, 72, 224, 16, 151, 195, 52, 23, 159, 178, 19, 161, 250, 40, 127, 74, 140, 124, 239, 113, 2, 17, 0, 0, 0, 2, 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