Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3cce35b1d86e756d7281fccafb817496f2c3c54c02df2f753d86f2dfbcfa31e

Tx prefix hash: 2640e77c0a54fdbbf23f0a91e861d87fb65627fcdd9d7614acab91ff20f1beab
Tx public key: b033e1debe5f0baca6067c095ca519f6fc9b9d80d60abd4377e9a7f933b23d59
Timestamp: 1708725446 Timestamp [UTC]: 2024-02-23 21:57:26 Age [y:d:h:m:s]: 02:117:16:11:24
Block: 964085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599802 RingCT/type: yes/0
Extra: 01b033e1debe5f0baca6067c095ca519f6fc9b9d80d60abd4377e9a7f933b23d5902110000000a59dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0354b32fe61abc5fc80ce5b011cfb80b8bf2b3db90d92f1cdc8935718d81e36f 0.000600000000 1423812 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": 964095, "vin": [ { "gen": { "height": 964085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0354b32fe61abc5fc80ce5b011cfb80b8bf2b3db90d92f1cdc8935718d81e36f" } } ], "extra": [ 1, 176, 51, 225, 222, 190, 95, 11, 172, 166, 6, 124, 9, 92, 165, 25, 246, 252, 155, 157, 128, 214, 10, 189, 67, 119, 233, 167, 249, 51, 178, 61, 89, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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: