Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba304e67ed989616dec0960e20f7c632ef28a0a50bf28a714d2cd73ccef5440c

Tx prefix hash: ae8ec7f2d36b0477227c6e1396f8c3f7ce9244c5b450d3f62e13a09ebf7d7950
Tx public key: 32e0140ba803dd0134f8f6a04fc8f0611b2935125c7dfd36c6ddd92ad528a04b
Timestamp: 1772993816 Timestamp [UTC]: 2026-03-08 18:16:56 Age [y:d:h:m:s]: 00:257:18:44:12
Block: 1493528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189890 RingCT/type: yes/0
Extra: 0132e0140ba803dd0134f8f6a04fc8f0611b2935125c7dfd36c6ddd92ad528a04b021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 59b101cbbb718059a363b94aa191d3607e05baff8179ffaa075bbf1a4d77b66d 0.000600000000 1983088 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": 1493538, "vin": [ { "gen": { "height": 1493528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59b101cbbb718059a363b94aa191d3607e05baff8179ffaa075bbf1a4d77b66d" } } ], "extra": [ 1, 50, 224, 20, 11, 168, 3, 221, 1, 52, 248, 246, 160, 79, 200, 240, 97, 27, 41, 53, 18, 92, 125, 253, 54, 198, 221, 217, 42, 213, 40, 160, 75, 2, 17, 0, 0, 0, 8, 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: