← previous blocknext block →recent activity
Analyzing
Block #83,890,511
31 transactions · 22 stateful · 2026-06-26 20:44:35 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,890,511 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w211w319w322w023w425w426w528w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff96dc9b…93d7
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x6f915004…a881
0xd32edf…ff58
7 touches
6 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0xff96dc9b2f…5a93d7
Audit this contract →
← previous block·next block →recent activity