Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a00bead1b95372d1440c6f2e0a1b4ffba27a1cafc3ca9a19de4aeddb91727bab

Tx prefix hash: e9aed4bc3f9dde0405755186f6fbc7d1daa75b84951516e00e0da4efd2e99015
Tx public key: e001071d571209dbe3337923a011ddf9182f088ab074be4b56f4dab5610d6129
Timestamp: 1741445189 Timestamp [UTC]: 2025-03-08 14:46:29 Age [y:d:h:m:s]: 00:344:03:14:20
Block: 1234889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243606 RingCT/type: yes/0
Extra: 01e001071d571209dbe3337923a011ddf9182f088ab074be4b56f4dab5610d61290211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 05ec3feb5115101f61d3b6d89f8813d9b12563d07c58e1a425affe3460f40aef 0.000600000000 1721824 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": 1234899, "vin": [ { "gen": { "height": 1234889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05ec3feb5115101f61d3b6d89f8813d9b12563d07c58e1a425affe3460f40aef" } } ], "extra": [ 1, 224, 1, 7, 29, 87, 18, 9, 219, 227, 51, 121, 35, 160, 17, 221, 249, 24, 47, 8, 138, 176, 116, 190, 75, 86, 244, 218, 181, 97, 13, 97, 41, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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) | dinastycoin version: tesla-369