Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0c5b889b2dd3ef2e2a39be5827a5b2d95cd54dbb56359be4ab1d838fe371227

Tx prefix hash: 0aa00916d75f6f941d0c53b9bff087d5939e3e9e3d619368590118ac8eec7eb5
Tx public key: e4e21f06d2d8ce79e5f73f5290c49ca4913efabe1ab2d15fe4db4d06ec9f6567
Timestamp: 1753304091 Timestamp [UTC]: 2025-07-23 20:54:51 Age [y:d:h:m:s]: 01:116:00:01:32
Block: 1331896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347998 RingCT/type: yes/0
Extra: 01e4e21f06d2d8ce79e5f73f5290c49ca4913efabe1ab2d15fe4db4d06ec9f65670211000000028368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a787b3e0b1d3eb3edb3c5fa163dda4beb5ad19bb502ad7ebffb524e812d63698 0.000600000000 1819693 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": 1331906, "vin": [ { "gen": { "height": 1331896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a787b3e0b1d3eb3edb3c5fa163dda4beb5ad19bb502ad7ebffb524e812d63698" } } ], "extra": [ 1, 228, 226, 31, 6, 210, 216, 206, 121, 229, 247, 63, 82, 144, 196, 156, 164, 145, 62, 250, 190, 26, 178, 209, 95, 228, 219, 77, 6, 236, 159, 101, 103, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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: