Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4254f5fc12d62bec7ba62d885b4d7dbc83ace15d35f952f8ea08eccfd32ac148

Tx prefix hash: 0e410ba9a503d64eff450b518398502cafdabcbb99262313e4b26456418f706e
Tx public key: 9e21563468de4bef74052a4eb0176e67ebb1ac1b14cf0e4be8f19c3b53c156c8
Timestamp: 1761019471 Timestamp [UTC]: 2025-10-21 04:04:31 Age [y:d:h:m:s]: 01:025:04:23:04
Block: 1394524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284244 RingCT/type: yes/0
Extra: 019e21563468de4bef74052a4eb0176e67ebb1ac1b14cf0e4be8f19c3b53c156c8021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9cd32c749eb0f86a01dfdda881d206ad4a13ade67412f64df071d3807df9c6e2 0.000600000000 1882795 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": 1394534, "vin": [ { "gen": { "height": 1394524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cd32c749eb0f86a01dfdda881d206ad4a13ade67412f64df071d3807df9c6e2" } } ], "extra": [ 1, 158, 33, 86, 52, 104, 222, 75, 239, 116, 5, 42, 78, 176, 23, 110, 103, 235, 177, 172, 27, 20, 207, 14, 75, 232, 241, 156, 59, 83, 193, 86, 200, 2, 17, 0, 0, 0, 1, 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: