Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 345fd53b86df7481f354824185895cfee4fa878fe95467b642c0bebc7e16a75c

Tx prefix hash: 20eb6ad221df10ae7bf76953eaad0ec80023810c51dfc8f236207461583837ef
Tx public key: ce9fe2e06044186adb87dbfd18078c3ee7d8dcf8d06a738c1e72d91b6f1908f9
Timestamp: 1750080959 Timestamp [UTC]: 2025-06-16 13:35:59 Age [y:d:h:m:s]: 00:329:19:14:28
Block: 1306259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225732 RingCT/type: yes/0
Extra: 01ce9fe2e06044186adb87dbfd18078c3ee7d8dcf8d06a738c1e72d91b6f1908f902110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 20095ef9d778d3661fa5bdabb62b1ec1147a44bd1bb02f81da3c4677c55d3e1c 0.000600000000 1793862 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": 1306269, "vin": [ { "gen": { "height": 1306259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20095ef9d778d3661fa5bdabb62b1ec1147a44bd1bb02f81da3c4677c55d3e1c" } } ], "extra": [ 1, 206, 159, 226, 224, 96, 68, 24, 106, 219, 135, 219, 253, 24, 7, 140, 62, 231, 216, 220, 248, 208, 106, 115, 140, 30, 114, 217, 27, 111, 25, 8, 249, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: