Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c66edf9b03f0643bea48fe5a548cad458dc43e8d377c404abc29ff5994826199

Tx prefix hash: 19bcb45fe6f3c5598be6302e546d3a1eeac96b3af9d490fe87e04b1d6c3830ef
Tx public key: 0f503e850d88deb775b5d4d8552d7fd3c318bfcba78f29ad6e48cbe549cc88f8
Timestamp: 1591870554 Timestamp [UTC]: 2020-06-11 10:15:54 Age [y:d:h:m:s]: 05:342:05:49:46
Block: 107129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1429659 RingCT/type: yes/0
Extra: 010f503e850d88deb775b5d4d8552d7fd3c318bfcba78f29ad6e48cbe549cc88f80211000000027db0bdeb000000000000000000

1 output(s) for total of 0.271042817939 xmr

stealth address amount amount idx tag
00: 13a7b29295f17b407a524c82b65d00f0c59699aa25be80ed26f12148e8c40eec 0.271042817939 186718 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 dinastycoin-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": 107139, "vin": [ { "gen": { "height": 107129 } } ], "vout": [ { "amount": 271042817939, "target": { "key": "13a7b29295f17b407a524c82b65d00f0c59699aa25be80ed26f12148e8c40eec" } } ], "extra": [ 1, 15, 80, 62, 133, 13, 136, 222, 183, 117, 181, 212, 216, 85, 45, 127, 211, 195, 24, 191, 203, 167, 143, 41, 173, 110, 72, 203, 229, 73, 204, 136, 248, 2, 17, 0, 0, 0, 2, 125, 176, 189, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: