Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ed9b3cd62997e7ad4d340ac457294c803c5e452e4595bdb4e6dab6596c2150c

Tx prefix hash: 40e9d4d1eb8ce379571d71cb45e3f2f0ed2f05ea38882b16e4865864f5adf78f
Tx public key: 69b3793a9f43c61783db84c5db2a9be81037e96d47dc5d85af24d1f077cc63f8
Timestamp: 1774121398 Timestamp [UTC]: 2026-03-21 19:29:58 Age [y:d:h:m:s]: 00:244:22:33:04
Block: 1502836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180658 RingCT/type: yes/0
Extra: 0169b3793a9f43c61783db84c5db2a9be81037e96d47dc5d85af24d1f077cc63f8021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 05beb6aab968da9ba1e1a3c8d013e3ce0bb39008d3eac4afb6b7b42331f74843 0.000600000000 1992538 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": 1502846, "vin": [ { "gen": { "height": 1502836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05beb6aab968da9ba1e1a3c8d013e3ce0bb39008d3eac4afb6b7b42331f74843" } } ], "extra": [ 1, 105, 179, 121, 58, 159, 67, 198, 23, 131, 219, 132, 197, 219, 42, 155, 232, 16, 55, 233, 109, 71, 220, 93, 133, 175, 36, 209, 240, 119, 204, 99, 248, 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: