Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da980f42012d7c095e269e0e29154566f85c9a0f3e7d77ae8302aae435cc4c20

Tx prefix hash: c0ab6b3d5b6b358c61000cca6772859c47fe48d6bff3d293d3daf78bde2ebd76
Tx public key: fea370e8e37c7f5820fd2a312ef757e2024b04a6a419e4b8f880312a5d6bac68
Timestamp: 1751725380 Timestamp [UTC]: 2025-07-05 14:23:00 Age [y:d:h:m:s]: 00:314:20:46:44
Block: 1319302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215745 RingCT/type: yes/0
Extra: 01fea370e8e37c7f5820fd2a312ef757e2024b04a6a419e4b8f880312a5d6bac68021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c553d487a22231533e9907c10ae19d22c65a25bc3adf4b3100ae96c3cf7601c6 0.000600000000 1806993 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": 1319312, "vin": [ { "gen": { "height": 1319302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c553d487a22231533e9907c10ae19d22c65a25bc3adf4b3100ae96c3cf7601c6" } } ], "extra": [ 1, 254, 163, 112, 232, 227, 124, 127, 88, 32, 253, 42, 49, 46, 247, 87, 226, 2, 75, 4, 166, 164, 25, 228, 184, 248, 128, 49, 42, 93, 107, 172, 104, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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: