Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdfc1227ae8312ab9b8f65e191d9e0132c24382fe5d3c31ba896a707ea6b9dd0

Tx prefix hash: 111eef40b5652033a08d26aece68ce96839b494704790fc955d4a215d3f96dd5
Tx public key: b5404394e4ee39f7a616dc063f4ca5bef34b5549b5e55d69a4e86f3e5ace0a42
Timestamp: 1747959390 Timestamp [UTC]: 2025-05-23 00:16:30 Age [y:d:h:m:s]: 01:094:06:43:37
Block: 1288818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331700 RingCT/type: yes/0
Extra: 01b5404394e4ee39f7a616dc063f4ca5bef34b5549b5e55d69a4e86f3e5ace0a420211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e2cf32b7f0f580a9e61078cc0de1da2860719bc1c0593c9cb85601e167062877 0.000600000000 1776285 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": 1288828, "vin": [ { "gen": { "height": 1288818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2cf32b7f0f580a9e61078cc0de1da2860719bc1c0593c9cb85601e167062877" } } ], "extra": [ 1, 181, 64, 67, 148, 228, 238, 57, 247, 166, 22, 220, 6, 63, 76, 165, 190, 243, 75, 85, 73, 181, 229, 93, 105, 164, 232, 111, 62, 90, 206, 10, 66, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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: