Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ff0fb12cfe8cede1e8be4dd4af08934ab3411e8304861844e9cd58f0c7c2a3f

Tx prefix hash: 77fa4dfb1567818eb13324847e05300bf0b0e0011da4fc60a958395dc07d864d
Tx public key: f827a0f42fc783db6c3f11c6e8bb2d3be3f9d16dbec11ba4e54d34d2f76dcb5e
Timestamp: 1782787511 Timestamp [UTC]: 2026-06-30 02:45:11 Age [y:d:h:m:s]: 00:145:08:09:47
Block: 1571179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 112315 RingCT/type: yes/0
Extra: 01f827a0f42fc783db6c3f11c6e8bb2d3be3f9d16dbec11ba4e54d34d2f76dcb5e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: edca0e7886566e8283f1fa14b8438d412dd7b06efa9c1ae717fef2a8dd4e6b47 0.000600000000 2061159 of 15 <e8>

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": 1571189, "vin": [ { "gen": { "height": 1571179 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "edca0e7886566e8283f1fa14b8438d412dd7b06efa9c1ae717fef2a8dd4e6b47", "view_tag": "e8" } } } ], "extra": [ 1, 248, 39, 160, 244, 47, 199, 131, 219, 108, 63, 17, 198, 232, 187, 45, 59, 227, 249, 209, 109, 190, 193, 27, 164, 229, 77, 52, 210, 247, 109, 203, 94 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: