Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43ff7426e8ee28982807bbc99a09a7e71fbb47cd1f0b0a61c5ddcd7f17fe3b6c

Tx prefix hash: a42475a976022f0052c5a904b556f59bbd9c7978519e28b1bf27afc18e68e2a1
Tx public key: 01284c78031febf744794292717896a5b6ccaf37c765e2a424f2d2ee059bf661
Timestamp: 1773009406 Timestamp [UTC]: 2026-03-08 22:36:46 Age [y:d:h:m:s]: 00:251:05:32:08
Block: 1493661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184969 RingCT/type: yes/0
Extra: 0101284c78031febf744794292717896a5b6ccaf37c765e2a424f2d2ee059bf661021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 193a9f53a9868f67de60baa5a1c280702da95189d48fa17aa58c190362f3ba4c 0.000600000000 1983221 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 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": 1493671, "vin": [ { "gen": { "height": 1493661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "193a9f53a9868f67de60baa5a1c280702da95189d48fa17aa58c190362f3ba4c" } } ], "extra": [ 1, 1, 40, 76, 120, 3, 31, 235, 247, 68, 121, 66, 146, 113, 120, 150, 165, 182, 204, 175, 55, 199, 101, 226, 164, 36, 242, 210, 238, 5, 155, 246, 97, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 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: