← previous blocknext block →recent activity
Analyzing
Block #105,642,807
43 transactions · 26 stateful · 2026-09-17 15:36:50 UTC
Parallelism
91/100
Blocked
58%
Avg conflicts / tx
0.51
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,642,807 · 43 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w210w211w012w113w214w315w320w021w122w123w225w335w336w037w339w141w042w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86bd79a5…1f48
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x669a2a6a…ba68
0xa6afd3…d132
5 touches
3 conflicts
0x2ebca8cf…e7bf
0xd32edf…ff58
5 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x86bd79a5a6…961f48
Audit this contract →
← previous block·next block →recent activity