Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4773fc39ed0c5d5577dfca6144d93bc0c7655a1c8ed8385b3bae4209216de43

Tx prefix hash: 9f0d041dac056bdb3bc48a6dc9a3a844308fc72020cdff8a129046ccdef2e5ab
Tx public key: fe0dedf42bad5737929900aadda54547ca45b4f6cc3f13971dc757ee603c1208
Timestamp: 1747832680 Timestamp [UTC]: 2025-05-21 13:04:40 Age [y:d:h:m:s]: 01:181:05:01:30
Block: 1287774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393527 RingCT/type: yes/0
Extra: 01fe0dedf42bad5737929900aadda54547ca45b4f6cc3f13971dc757ee603c12080211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d0bbd0df6a33722d3b3e0f998ce76867e317275d36a4e0c67f7be188ab266f9f 0.000600000000 1775241 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": 1287784, "vin": [ { "gen": { "height": 1287774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0bbd0df6a33722d3b3e0f998ce76867e317275d36a4e0c67f7be188ab266f9f" } } ], "extra": [ 1, 254, 13, 237, 244, 43, 173, 87, 55, 146, 153, 0, 170, 221, 165, 69, 71, 202, 69, 180, 246, 204, 63, 19, 151, 29, 199, 87, 238, 96, 60, 18, 8, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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: