Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 703c1040a696f48d5bfbedee422237d23b3594b5fceee8cba2a5c0e14dd76deb

Tx prefix hash: 98c91d6b343ac9d3ae68731b8354d4dcbdbc0aa5e34ed8268207936005395e6c
Tx public key: 6ff3a72ea4833ae607bb5f191737fd9166186e891fa006e057f02921a1f41be5
Timestamp: 1774405987 Timestamp [UTC]: 2026-03-25 02:33:07 Age [y:d:h:m:s]: 00:237:02:30:46
Block: 1505205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174954 RingCT/type: yes/0
Extra: 016ff3a72ea4833ae607bb5f191737fd9166186e891fa006e057f02921a1f41be5021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b1259e59577f8a0c417ab50537a24784c545cbcf4b275327fb234140f0863ecb 0.000600000000 1994937 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": 1505215, "vin": [ { "gen": { "height": 1505205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1259e59577f8a0c417ab50537a24784c545cbcf4b275327fb234140f0863ecb" } } ], "extra": [ 1, 111, 243, 167, 46, 164, 131, 58, 230, 7, 187, 95, 25, 23, 55, 253, 145, 102, 24, 110, 137, 31, 160, 6, 224, 87, 240, 41, 33, 161, 244, 27, 229, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: