← previous blocknext block →recent activity
Analyzing
Block #105,852,291
42 transactions · 40 stateful · 2026-09-18 09:12:36 UTC
Parallelism
55/100
Blocked
78%
Avg conflicts / tx
3.21
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #105,852,291 · 42 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w16w07w18w29w412w220w322w523w624w725w826w938w440w641w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x831f75b4…945d
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xc7b7b345…1d04
0x34b655…2a6f
16 touches
28 conflicts
0x6caf33e2…c261
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0x52d2a8f9…c94f
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0x831f75b4aa…17945d
Audit this contract →
← previous block·next block →recent activity