← previous blocknext block →recent activity
Analyzing
Block #105,852,935
23 transactions · 21 stateful · 2026-09-18 09:15:50 UTC
Parallelism
57/100
Blocked
52%
Avg conflicts / tx
1.65
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,852,935 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w110w111w212w313w414w515w416w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7ae06eb…aff5
0x34b655…2a6f
12 touches
15 conflicts
0x55192654…91fe
0x34b655…2a6f
12 touches
15 conflicts
0x675ee4ca…2455
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x206f4379…e08a
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x18978822…2623
0x34b655…2a6f
8 touches
6 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 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: Perpl
15 conflicts on slot 0xe7ae06eb70…40aff5
Audit this contract →
← previous block·next block →recent activity