Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cfa9b2d5911bd3dfecc1fc843f5841fbd5c13b996da20fae0eb7e7871e7b359

Tx prefix hash: 119e3c559c05e39bb80eadf0e1231e1ab39f78cf93dca2e1157dc49bfad94388
Tx public key: 6fdf52659fd812fba17cc22e4f504cc9f4becc9c5d2c82162907299f457db872
Timestamp: 1761288631 Timestamp [UCT]: 2025-10-24 06:50:31 Age [y:d:h:m:s]: 00:016:17:57:24
Block: 1396754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11978 RingCT/type: yes/0
Extra: 016fdf52659fd812fba17cc22e4f504cc9f4becc9c5d2c82162907299f457db872021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96b9153ec64e8154e7d1677edd5f8225ce522e3bc092e516da12840d9e8f8ab0 0.600000000000 1885041 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": 1396764, "vin": [ { "gen": { "height": 1396754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96b9153ec64e8154e7d1677edd5f8225ce522e3bc092e516da12840d9e8f8ab0" } } ], "extra": [ 1, 111, 223, 82, 101, 159, 216, 18, 251, 161, 124, 194, 46, 79, 80, 76, 201, 244, 190, 204, 156, 93, 44, 130, 22, 41, 7, 41, 159, 69, 125, 184, 114, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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