Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f269acbd5ef1e6c5ea97d9c0af5e7afc2f248be5baad03e07a125dd6b3b6278

Tx prefix hash: 2843209faba90359ca0741edcbcc09062dde1cc9ce6b34ffec12da301da59a15
Tx public key: 826ec04f791fa581225042e25780d0c0e2da5c53ebfef4f0ba1d927cb2adbf14
Timestamp: 1733718374 Timestamp [UCT]: 2024-12-09 04:26:14 Age [y:d:h:m:s]: 00:332:06:18:50
Block: 1171184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234959 RingCT/type: yes/0
Extra: 01826ec04f791fa581225042e25780d0c0e2da5c53ebfef4f0ba1d927cb2adbf140211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2da540e63938c62a744c3a06a93a20afb2f65b8348a24170b80db5b85cd9a2bf 0.600000000000 1656923 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": 1171194, "vin": [ { "gen": { "height": 1171184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2da540e63938c62a744c3a06a93a20afb2f65b8348a24170b80db5b85cd9a2bf" } } ], "extra": [ 1, 130, 110, 192, 79, 121, 31, 165, 129, 34, 80, 66, 226, 87, 128, 208, 192, 226, 218, 92, 83, 235, 254, 244, 240, 186, 29, 146, 124, 178, 173, 191, 20, 2, 17, 0, 0, 0, 1, 31, 10, 83, 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