Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 596f13bf02b0e5568cb11feb120a5b916c9b88d608239abfdbc1273d9a93e4dc

Tx prefix hash: 3816b02fc9cb819a5e029dd357948a40cce901862df7b3fd30344584a1518a47
Tx public key: 9c9a3d155c33e657a303ad1d0e99c67c51328e22176dbb846de93a7cf0edd951
Timestamp: 1773125142 Timestamp [UTC]: 2026-03-10 06:45:42 Age [y:d:h:m:s]: 00:255:09:04:00
Block: 1494609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188192 RingCT/type: yes/0
Extra: 019c9a3d155c33e657a303ad1d0e99c67c51328e22176dbb846de93a7cf0edd951021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e29916b3dfa447b443a97b9c4412e078a1eeedef75a1376c51c7e1281e1f1668 0.000600000000 1984181 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": 1494619, "vin": [ { "gen": { "height": 1494609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e29916b3dfa447b443a97b9c4412e078a1eeedef75a1376c51c7e1281e1f1668" } } ], "extra": [ 1, 156, 154, 61, 21, 92, 51, 230, 87, 163, 3, 173, 29, 14, 153, 198, 124, 81, 50, 142, 34, 23, 109, 187, 132, 109, 233, 58, 124, 240, 237, 217, 81, 2, 17, 0, 0, 0, 2, 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: