Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0fe98a618310f5fa2782aa52a2c49d5901f17f6352b2895b96bf1f5c3292eaa

Tx prefix hash: b5c91d1eb82bde714385e7b8baa139170d6496a8d35a70969cbb0ab77e91578b
Tx public key: 21d2b8d5f1841b1d943a1c66195d0394c4f9ff23b726d2adf3134b77641f120d
Timestamp: 1773567821 Timestamp [UTC]: 2026-03-15 09:43:41 Age [y:d:h:m:s]: 00:063:21:06:11
Block: 1498294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38188 RingCT/type: yes/0
Extra: 0121d2b8d5f1841b1d943a1c66195d0394c4f9ff23b726d2adf3134b77641f120d021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf5914c149b08655bee8b2bb98a90993286442f3e9d14c64dbd0d35f61b610b5 0.000600000000 1987940 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": 1498304, "vin": [ { "gen": { "height": 1498294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5914c149b08655bee8b2bb98a90993286442f3e9d14c64dbd0d35f61b610b5" } } ], "extra": [ 1, 33, 210, 184, 213, 241, 132, 27, 29, 148, 58, 28, 102, 25, 93, 3, 148, 196, 249, 255, 35, 183, 38, 210, 173, 243, 19, 75, 119, 100, 31, 18, 13, 2, 17, 0, 0, 0, 1, 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: