Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac8d211f41c201ed9fce226bfb5ac040565cbc7bdf4bd1befd9f751775b373d

Tx prefix hash: 6596f1f8917b6fdb33b1390b164f37a77342260e56aabf7c10712a79d29cab38
Tx public key: cef0bf1e2e175f600ccdab59da6fbfbb17f39fe0448a117e99b97d8a10ad5052
Timestamp: 1758773052 Timestamp [UTC]: 2025-09-25 04:04:12 Age [y:d:h:m:s]: 01:051:11:17:56
Block: 1375883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303101 RingCT/type: yes/0
Extra: 01cef0bf1e2e175f600ccdab59da6fbfbb17f39fe0448a117e99b97d8a10ad5052021100000004ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8195f491cea0c070d90212ec9a2836fa96181d9f7d2b2e13a1690f4699ba9997 0.000600000000 1863974 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": 1375893, "vin": [ { "gen": { "height": 1375883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8195f491cea0c070d90212ec9a2836fa96181d9f7d2b2e13a1690f4699ba9997" } } ], "extra": [ 1, 206, 240, 191, 30, 46, 23, 95, 96, 12, 205, 171, 89, 218, 111, 191, 187, 23, 243, 159, 224, 68, 138, 17, 126, 153, 185, 125, 138, 16, 173, 80, 82, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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: