Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2df6d1ad5be35437fc4a380e6658858fac7fdea67606f63505555f59f4d7dde

Tx prefix hash: bf0b65e1c7cc6844724e38910e744430d90f9c580e50ae7c7874df36ab56682c
Tx public key: dd65a23a41210602bc7635b3ab2888e37ce6ecce7dda6eea2958479a5d78301b
Timestamp: 1771870852 Timestamp [UTC]: 2026-02-23 18:20:52 Age [y:d:h:m:s]: 00:269:00:31:41
Block: 1484240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197847 RingCT/type: yes/0
Extra: 01dd65a23a41210602bc7635b3ab2888e37ce6ecce7dda6eea2958479a5d78301b021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f2eee181334ac5ac3f62d19336a440cca870e4cf7f13dbb42e62f2c12dfbcd5 0.000600000000 1973660 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": 1484250, "vin": [ { "gen": { "height": 1484240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f2eee181334ac5ac3f62d19336a440cca870e4cf7f13dbb42e62f2c12dfbcd5" } } ], "extra": [ 1, 221, 101, 162, 58, 65, 33, 6, 2, 188, 118, 53, 179, 171, 40, 136, 227, 124, 230, 236, 206, 125, 218, 110, 234, 41, 88, 71, 154, 93, 120, 48, 27, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: