Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b9b98aa1225f77a589ab87096defb46ed77574c36f8a7f803ffff9c8d07d0d

Tx prefix hash: f230ec4c774160e1c3d3ca89a9a51558700da4e256abc6a517aa30fa97f6368a
Tx public key: 50a08cd6076d17d633f31beb5d9a656600bc864ee8dca50ce342b59e2b7b6192
Timestamp: 1678664198 Timestamp [UTC]: 2023-03-12 23:36:38 Age [y:d:h:m:s]: 03:252:00:54:13
Block: 715758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 965747 RingCT/type: yes/0
Extra: 0150a08cd6076d17d633f31beb5d9a656600bc864ee8dca50ce342b59e2b7b61920211000000015029cbac000000000000000000

1 output(s) for total of 0.002608534055 xmr

stealth address amount amount idx tag
00: 7869a2c1152790c08dbe0cc7b8508e7c93adac9b66d883390017b0194deb2214 0.002608534055 1160067 of 0 -

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": 715768, "vin": [ { "gen": { "height": 715758 } } ], "vout": [ { "amount": 2608534055, "target": { "key": "7869a2c1152790c08dbe0cc7b8508e7c93adac9b66d883390017b0194deb2214" } } ], "extra": [ 1, 80, 160, 140, 214, 7, 109, 23, 214, 51, 243, 27, 235, 93, 154, 101, 102, 0, 188, 134, 78, 232, 220, 165, 12, 227, 66, 181, 158, 43, 123, 97, 146, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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: