Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddfd936aa861effb89eb7d475ee3e0e9e35f21ff6f9e0ff231bb44f82989a7bb

Tx prefix hash: c7e01af923be0edd24ca61809a52c9a5e7271bf837644482d1e3e9defa5cb14d
Tx public key: e646d3e0d0d40b18d9af0aa9462e56bc0137dc60fcc74097ea54fe913c646e82
Timestamp: 1755598971 Timestamp [UTC]: 2025-08-19 10:22:51 Age [y:d:h:m:s]: 01:092:13:07:56
Block: 1349792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332446 RingCT/type: yes/0
Extra: 01e646d3e0d0d40b18d9af0aa9462e56bc0137dc60fcc74097ea54fe913c646e82021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1d6122af7a3ed15832eac5b242be9775cd88319c32617b562f43ea8f573780c0 0.000600000000 1837727 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": 1349802, "vin": [ { "gen": { "height": 1349792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d6122af7a3ed15832eac5b242be9775cd88319c32617b562f43ea8f573780c0" } } ], "extra": [ 1, 230, 70, 211, 224, 208, 212, 11, 24, 217, 175, 10, 169, 70, 46, 86, 188, 1, 55, 220, 96, 252, 199, 64, 151, 234, 84, 254, 145, 60, 100, 110, 130, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: