Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16de8fcc1cd88cb00e27c789fca3f45916398a10ebef34220378b4a111cc673e

Tx prefix hash: 98466a5810d022b2572aea205587625306589163e1c58250ce69b373c4bab38a
Tx public key: 8c7faf6bd29a43a5696fa6b4d6201c4508be99f7d3aac962790a7d81537cf4f2
Timestamp: 1695127767 Timestamp [UCT]: 2023-09-19 12:49:27 Age [y:d:h:m:s]: 01:001:04:23:43
Block: 851540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262103 RingCT/type: yes/0
Extra: 018c7faf6bd29a43a5696fa6b4d6201c4508be99f7d3aac962790a7d81537cf4f2021100000001d4dbf7b9000000000000000000

1 output(s) for total of 0.925751753000 dcy

stealth address amount amount idx
00: 390fef7de7af4fa1c7ffd70c9f0d5bd4dadbb8381c64d5d1c48b1e4253131ed4 0.925751753000 1305330 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": 851550, "vin": [ { "gen": { "height": 851540 } } ], "vout": [ { "amount": 925751753, "target": { "key": "390fef7de7af4fa1c7ffd70c9f0d5bd4dadbb8381c64d5d1c48b1e4253131ed4" } } ], "extra": [ 1, 140, 127, 175, 107, 210, 154, 67, 165, 105, 111, 166, 180, 214, 32, 28, 69, 8, 190, 153, 247, 211, 170, 201, 98, 121, 10, 125, 129, 83, 124, 244, 242, 2, 17, 0, 0, 0, 1, 212, 219, 247, 185, 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