Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 658b2edc8048a9001b1a267878ba3d41b9acf43d6af1af67735bc4f8aae3dd7c

Tx prefix hash: 69f9021e99494c3c0f5ed62a21f44c1f9d0fbd2235534cef2d4449ee0c58d37d
Tx public key: 3aeaa6ac49f36f44cc808106f8dc3729a2579d44359128cc575171905fb0f9df
Timestamp: 1744815642 Timestamp [UTC]: 2025-04-16 15:00:42 Age [y:d:h:m:s]: 01:033:22:28:07
Block: 1262787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276233 RingCT/type: yes/0
Extra: 013aeaa6ac49f36f44cc808106f8dc3729a2579d44359128cc575171905fb0f9df0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8ac34d367bd4d7bb57f1dea0c48710870403d713609491006cb9e049949e6efe 0.000600000000 1749970 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": 1262797, "vin": [ { "gen": { "height": 1262787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ac34d367bd4d7bb57f1dea0c48710870403d713609491006cb9e049949e6efe" } } ], "extra": [ 1, 58, 234, 166, 172, 73, 243, 111, 68, 204, 128, 129, 6, 248, 220, 55, 41, 162, 87, 157, 68, 53, 145, 40, 204, 87, 81, 113, 144, 95, 176, 249, 223, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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: