← previous blocknext block →recent activity
Analyzing
Block #105,843,301
20 transactions · 19 stateful · 2026-09-18 08:27:18 UTC
Parallelism
60/100
Blocked
42%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,843,301 · 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
9w010w111w212w313w414w515w616w719w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x8db32935…81a7
0x34b655…2a6f
16 touches
28 conflicts
0xc125f6c9…07f6
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd64d27de…28a9
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
8 touches
6 conflicts
0xf71da675…4671
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity