Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 595034bb660270fa50f3505ca0cecd9bb9785728d3515bb792719b79e181cb1b

Tx prefix hash: ca31591e9675fe7cd06b22e3220e608b97d228c2112d9d22e28e641aa43bf034
Tx public key: 777ac43f2ccc6801cd86f7f7de42b9d5423d041078544a8c9bf490301e46e098
Timestamp: 1722161151 Timestamp [UTC]: 2024-07-28 10:05:51 Age [y:d:h:m:s]: 02:116:09:23:32
Block: 1075471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608023 RingCT/type: yes/0
Extra: 01777ac43f2ccc6801cd86f7f7de42b9d5423d041078544a8c9bf490301e46e09802110000000d91e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0f8afee24f37b74f8becd85d33e483ab5d415a8b14242d0df19fe0be0e275cbb 0.000600000000 1548000 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": 1075481, "vin": [ { "gen": { "height": 1075471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f8afee24f37b74f8becd85d33e483ab5d415a8b14242d0df19fe0be0e275cbb" } } ], "extra": [ 1, 119, 122, 196, 63, 44, 204, 104, 1, 205, 134, 247, 247, 222, 66, 185, 213, 66, 61, 4, 16, 120, 84, 74, 140, 155, 244, 144, 48, 30, 70, 224, 152, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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: