Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2616ce1b54c4053645dd9cee42e51083bb2b1e691c32574d4fd5b36e70794b0

Tx prefix hash: 02f8f1fe158efe166d984e8d10cef66ccf768c3f4a3c5d8af00a9f135529dcda
Tx public key: fd6fcbd08ca92c579d7718306091e9e9bf8736aececdca81a9480664814e475c
Timestamp: 1735256278 Timestamp [UCT]: 2024-12-26 23:37:58 Age [y:d:h:m:s]: 00:092:12:45:33
Block: 1183900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65930 RingCT/type: yes/0
Extra: 01fd6fcbd08ca92c579d7718306091e9e9bf8736aececdca81a9480664814e475c021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deb3659b9f8128750febeb3db89f31f96b3f4f7d7a598b627a593d721764aa82 0.600000000000 1670349 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": 1183910, "vin": [ { "gen": { "height": 1183900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deb3659b9f8128750febeb3db89f31f96b3f4f7d7a598b627a593d721764aa82" } } ], "extra": [ 1, 253, 111, 203, 208, 140, 169, 44, 87, 157, 119, 24, 48, 96, 145, 233, 233, 191, 135, 54, 174, 206, 205, 202, 129, 169, 72, 6, 100, 129, 78, 71, 92, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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