← previous blocknext block →recent activity
Analyzing
Block #111,666,880
39 transactions · 31 stateful · 2026-10-08 17:14:30 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #111,666,880 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
16 touches
28 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0x65bd465d…9770
0x34b655…2a6f
6 touches
3 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
6 touches
3 conflicts
0xfdb01200…062a
0x34b655…2a6f
6 touches
3 conflicts
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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity