Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38e14e3784b2d85058c5116ff5918df1d37fc9cf823d0cd8e52f4f82a6eb11ba

Tx prefix hash: 9339a8d65f5b520dbff44d44206fecec8f4b9eac4b12e902d0a84b40fd8b6f33
Tx public key: 4df58868079fb084c1d29f612a6d40d518a9c759f8a8b2c85badc5452ea59695
Timestamp: 1790842699 Timestamp [UTC]: 2026-10-01 08:18:19 Age [y:d:h:m:s]: 00:047:10:26:58
Block: 1646438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 34129 RingCT/type: yes/0
Extra: 014df58868079fb084c1d29f612a6d40d518a9c759f8a8b2c85badc5452ea59695

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2dc8a7b4f823cf76688d4a02a76ebcd28ea8cd96a7ca53fd2263a3b3e8449d9f 0.000600000000 2136594 of 15 <2f>

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": 1646448, "vin": [ { "gen": { "height": 1646438 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "2dc8a7b4f823cf76688d4a02a76ebcd28ea8cd96a7ca53fd2263a3b3e8449d9f", "view_tag": "2f" } } } ], "extra": [ 1, 77, 245, 136, 104, 7, 159, 176, 132, 193, 210, 159, 97, 42, 109, 64, 213, 24, 169, 199, 89, 248, 168, 178, 200, 91, 173, 197, 69, 46, 165, 150, 149 ], "rct_signatures": { "type": 0 } }


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