← previous blocknext block →recent activity
Analyzing
Block #105,844,773
20 transactions · 19 stateful · 2026-09-18 08:34:44 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,844,773 · 20 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
1w02w13w04w15w16w27w312w413w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa456132b…21c8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x8db32935…81a7
0x34b655…2a6f
12 touches
15 conflicts
0xd64d27de…28a9
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
8 touches
6 conflicts
0x69ba6585…48f4
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
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: Perpl
15 conflicts on slot 0xa456132b60…b421c8
Audit this contract →
← previous block·next block →recent activity