Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51ca12abdfb5d843de6d7fe1d0d71bb1a7ba8d3725e7d2756668e31b36b81785

Tx prefix hash: 9d913adc8fc28b3b6e5113eedd5c7fc3d6678f4edddf08fee5ab191e4fa04659
Tx public key: 10a2f61e2ba8932af325bd6cd9f4c4bb56bd27f5e15b5de2824f79676d22c84c
Timestamp: 1773828059 Timestamp [UTC]: 2026-03-18 10:00:59 Age [y:d:h:m:s]: 00:059:04:26:53
Block: 1500406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34747 RingCT/type: yes/0
Extra: 0110a2f61e2ba8932af325bd6cd9f4c4bb56bd27f5e15b5de2824f79676d22c84c021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4e0f404e8c643dc2785173242860f0563cc1dd8565590a9681b63a0268c61f09 0.000600000000 1990078 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": 1500416, "vin": [ { "gen": { "height": 1500406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e0f404e8c643dc2785173242860f0563cc1dd8565590a9681b63a0268c61f09" } } ], "extra": [ 1, 16, 162, 246, 30, 43, 168, 147, 42, 243, 37, 189, 108, 217, 244, 196, 187, 86, 189, 39, 245, 225, 91, 93, 226, 130, 79, 121, 103, 109, 34, 200, 76, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: