Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a29a7e0a219964df934770870e2abb1c9f3c7cddebf9c62c0daacf13d0e030d3

Tx prefix hash: 644f814b2a06509f70c9facf8a6305724dddc276a9587723c80b76158a99fcb8
Tx public key: 1e9e5c90fe87468470d4e612ccac6bdd5f57e88bcdd4c80e31cf38eeb74facfa
Timestamp: 1770161613 Timestamp [UTC]: 2026-02-03 23:33:33 Age [y:d:h:m:s]: 00:013:18:56:44
Block: 1470113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 9825 RingCT/type: yes/0
Extra: 011e9e5c90fe87468470d4e612ccac6bdd5f57e88bcdd4c80e31cf38eeb74facfa0208c7d9d03ad0a6ea51

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 066a2829b9e8dbbe44b8f515f6db5f99ea44b734039da3d7aa965821d3585066 0.000600000000 1959381 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": 1470123, "vin": [ { "gen": { "height": 1470113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "066a2829b9e8dbbe44b8f515f6db5f99ea44b734039da3d7aa965821d3585066" } } ], "extra": [ 1, 30, 158, 92, 144, 254, 135, 70, 132, 112, 212, 230, 18, 204, 172, 107, 221, 95, 87, 232, 139, 205, 212, 200, 14, 49, 207, 56, 238, 183, 79, 172, 250, 2, 8, 199, 217, 208, 58, 208, 166, 234, 81 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369