Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 962d4144da66c84ae29012fd6283fe760e1ce5bf1c433ec22f517e5911ff5540

Tx prefix hash: f54ac161db11ff7700d19f6e660eb8e6a051d412bd5a4f60e1be2473b0861e32
Tx public key: e46fadec7f60ece2916d9895d054b3fef3566e4f42b7c9e9b3f055f40820be46
Timestamp: 1579675158 Timestamp [UTC]: 2020-01-22 06:39:18 Age [y:d:h:m:s]: 06:305:19:22:01
Block: 50710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1632784 RingCT/type: yes/0
Extra: 01e46fadec7f60ece2916d9895d054b3fef3566e4f42b7c9e9b3f055f40820be46021100000016d81c26c0000000000000000000

1 output(s) for total of 0.416847835954 xmr

stealth address amount amount idx tag
00: 3e0571f57ba2b63551b94c549ee68c7b4c02d7f12bf563f7f5ea989e79a2df65 0.416847835954 94048 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": 50720, "vin": [ { "gen": { "height": 50710 } } ], "vout": [ { "amount": 416847835954, "target": { "key": "3e0571f57ba2b63551b94c549ee68c7b4c02d7f12bf563f7f5ea989e79a2df65" } } ], "extra": [ 1, 228, 111, 173, 236, 127, 96, 236, 226, 145, 109, 152, 149, 208, 84, 179, 254, 243, 86, 110, 79, 66, 183, 201, 233, 179, 240, 85, 244, 8, 32, 190, 70, 2, 17, 0, 0, 0, 22, 216, 28, 38, 192, 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: