Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fed5336f29f79f282fe187a3ab44710ea06951cd9a850ef6221b64cd3601e53d

Tx prefix hash: dbabbaddaa3fd864b5000be461563496362d1040d068dd4e7cba906ed20b268f
Tx public key: 8c7526eb831712f816aefef8750e5187fde11c4b8ab982e42fdbb232fe926dc7
Timestamp: 1747622505 Timestamp [UTC]: 2025-05-19 02:41:45 Age [y:d:h:m:s]: 00:356:02:04:01
Block: 1286014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244837 RingCT/type: yes/0
Extra: 018c7526eb831712f816aefef8750e5187fde11c4b8ab982e42fdbb232fe926dc70211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2bef567ad4aa979fa76554ce612c109c8327130f9180cd9b79db8c6bbee4f2c 0.000600000000 1773479 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": 1286024, "vin": [ { "gen": { "height": 1286014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2bef567ad4aa979fa76554ce612c109c8327130f9180cd9b79db8c6bbee4f2c" } } ], "extra": [ 1, 140, 117, 38, 235, 131, 23, 18, 248, 22, 174, 254, 248, 117, 14, 81, 135, 253, 225, 28, 75, 138, 185, 130, 228, 47, 219, 178, 50, 254, 146, 109, 199, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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: