Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed5dc2bb4513ba09fcb791480b081bf1189076e5fb1b617661a8c7c460f47bfb

Tx prefix hash: 59a9496fab5df3c286205484a15daced5cc49e33262e1494350538e7fb076cd7
Tx public key: 537cd156349fce52091cf95d5d34f5a07882cb4fadaf57b75db5d109f8a166d5
Timestamp: 1597532798 Timestamp [UTC]: 2020-08-15 23:06:38 Age [y:d:h:m:s]: 05:270:10:56:48
Block: 126835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1405194 RingCT/type: yes/0
Extra: 01537cd156349fce52091cf95d5d34f5a07882cb4fadaf57b75db5d109f8a166d50211000000084ac5aa02000000000000000000

1 output(s) for total of 0.233208146178 xmr

stealth address amount amount idx tag
00: 94b8aeae3aeacabac2758f63096a52c203892254b8f40cb286877de1c2cc3d23 0.233208146178 213865 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": 126845, "vin": [ { "gen": { "height": 126835 } } ], "vout": [ { "amount": 233208146178, "target": { "key": "94b8aeae3aeacabac2758f63096a52c203892254b8f40cb286877de1c2cc3d23" } } ], "extra": [ 1, 83, 124, 209, 86, 52, 159, 206, 82, 9, 28, 249, 93, 93, 52, 245, 160, 120, 130, 203, 79, 173, 175, 87, 183, 93, 181, 209, 9, 248, 161, 102, 213, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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: