Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8471b68b5f83d9f5c0c1e8e4856de2f2a83e2326f1bf8802fe75745e574acb6b

Tx prefix hash: fbae074071895ade02ec2387dfbf83e129701695581b0ab0cc2a6a4a7fae22f4
Tx public key: 5aa83387edca8207901525033ebcd90eeb57a84bc3cbdf9ff411f2d3062c8720
Timestamp: 1753283606 Timestamp [UTC]: 2025-07-23 15:13:26 Age [y:d:h:m:s]: 00:296:15:27:31
Block: 1331732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203204 RingCT/type: yes/0
Extra: 015aa83387edca8207901525033ebcd90eeb57a84bc3cbdf9ff411f2d3062c87200211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a77e42fe8ab1e432d96fcd9bb4c941c6c040631028ce35f878084bb22c61196e 0.000600000000 1819529 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": 1331742, "vin": [ { "gen": { "height": 1331732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a77e42fe8ab1e432d96fcd9bb4c941c6c040631028ce35f878084bb22c61196e" } } ], "extra": [ 1, 90, 168, 51, 135, 237, 202, 130, 7, 144, 21, 37, 3, 62, 188, 217, 14, 235, 87, 168, 75, 195, 203, 223, 159, 244, 17, 242, 211, 6, 44, 135, 32, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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: