Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3231f76ff624ad41a698d252724d696f60a4e10fa04ba741db364520c2b469ee

Tx prefix hash: 29ddc006476617c7d81077a529a96fd8219ea2158ad4ab90a0b8136d68eb805e
Tx public key: d3f2ac559947efc6148eae7f21858ff4e6e8192a05d1c2a5e475ca5394a31d19
Timestamp: 1745519072 Timestamp [UTC]: 2025-04-24 18:24:32 Age [y:d:h:m:s]: 01:203:03:14:28
Block: 1268607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409069 RingCT/type: yes/0
Extra: 01d3f2ac559947efc6148eae7f21858ff4e6e8192a05d1c2a5e475ca5394a31d190211000000096c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a01a5534863c17cd21ddb8c9122e1ef1e67d0811539b40a3c0740164512d4e2a 0.000600000000 1755836 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": 1268617, "vin": [ { "gen": { "height": 1268607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a01a5534863c17cd21ddb8c9122e1ef1e67d0811539b40a3c0740164512d4e2a" } } ], "extra": [ 1, 211, 242, 172, 85, 153, 71, 239, 198, 20, 142, 174, 127, 33, 133, 143, 244, 230, 232, 25, 42, 5, 209, 194, 165, 228, 117, 202, 83, 148, 163, 29, 25, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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: