Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4b3eefb24db53babb748bf6214c53ae077808968ea08e166e1a03e49925da06

Tx prefix hash: 4e8707d35980cb7a6ae7d54c6051334be6202bf4ca3510dfebbfb165a436dbd2
Tx public key: 789e014c618c577a9c1094164c475a6c9f1b7160ec81c0dfd224382eda290810
Timestamp: 1705256447 Timestamp [UCT]: 2024-01-14 18:20:47 Age [y:d:h:m:s]: 01:129:17:45:03
Block: 935315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353858 RingCT/type: yes/0
Extra: 01789e014c618c577a9c1094164c475a6c9f1b7160ec81c0dfd224382eda2908100211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c93c22bc9c615dd7ded98cbed5b13bb38ad7176b0f3abedc808e5f57d37cee8e 0.600000000000 1393331 of 15

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": 935325, "vin": [ { "gen": { "height": 935315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c93c22bc9c615dd7ded98cbed5b13bb38ad7176b0f3abedc808e5f57d37cee8e" } } ], "extra": [ 1, 120, 158, 1, 76, 97, 140, 87, 122, 156, 16, 148, 22, 76, 71, 90, 108, 159, 27, 113, 96, 236, 129, 192, 223, 210, 36, 56, 46, 218, 41, 8, 16, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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