Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6d502df5a39ef7ff2bf7fb305dea23219d86d01a680132233439f8b2c643b67

Tx prefix hash: 49315b886be5c1cdeda569b460d84b1f9b21c871b9de8e9a122022cbfbae5a47
Tx public key: 010642a7348ca3cbf392f18992d9d528ccffca41dfa327f8a50f196048e1ff0f
Timestamp: 1747477972 Timestamp [UTC]: 2025-05-17 10:32:52 Age [y:d:h:m:s]: 01:184:23:08:05
Block: 1284832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396212 RingCT/type: yes/0
Extra: 01010642a7348ca3cbf392f18992d9d528ccffca41dfa327f8a50f196048e1ff0f0211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fdcc521e699e353895016c80970467f859c3a3e09d19338e858d022e9c6ee42e 0.000600000000 1772295 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": 1284842, "vin": [ { "gen": { "height": 1284832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdcc521e699e353895016c80970467f859c3a3e09d19338e858d022e9c6ee42e" } } ], "extra": [ 1, 1, 6, 66, 167, 52, 140, 163, 203, 243, 146, 241, 137, 146, 217, 213, 40, 204, 255, 202, 65, 223, 163, 39, 248, 165, 15, 25, 96, 72, 225, 255, 15, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: