Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6af39ce5b00fa5bdaa3db9e59050aa0dd9aed0aeafa9372cc949bd1df2c5d028

Tx prefix hash: dd6eb4212d49b0f61db13a360a965f749cfdff736853b6e196d241a8331b0b8b
Tx public key: 3c3a16a465b218e0c534accd2537d0e90d1951eca022cbd13f5bc74d89a92de9
Timestamp: 1761886614 Timestamp [UTC]: 2025-10-31 04:56:54 Age [y:d:h:m:s]: 01:016:11:32:28
Block: 1401710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278059 RingCT/type: yes/0
Extra: 013c3a16a465b218e0c534accd2537d0e90d1951eca022cbd13f5bc74d89a92de902110000000ddf5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 06c0f479cfdce0f508690fd03a952f798c2f3db0294338e48962b0b3eb2a6e69 0.000600000000 1890029 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": 1401720, "vin": [ { "gen": { "height": 1401710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c0f479cfdce0f508690fd03a952f798c2f3db0294338e48962b0b3eb2a6e69" } } ], "extra": [ 1, 60, 58, 22, 164, 101, 178, 24, 224, 197, 52, 172, 205, 37, 55, 208, 233, 13, 25, 81, 236, 160, 34, 203, 209, 63, 91, 199, 77, 137, 169, 45, 233, 2, 17, 0, 0, 0, 13, 223, 90, 36, 122, 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: