← previous blocknext block →recent activity
Analyzing
Block #105,841,844
21 transactions · 19 stateful · 2026-09-18 08:19:53 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
1.38
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,841,844 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w210w213w314w415w516w617w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5871b087…587d
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x5684aadd…8d62
0x34b655…2a6f
10 touches
10 conflicts
0xc10b903d…2f54
0x34b655…2a6f
8 touches
6 conflicts
0xd336d408…1b00
0x34b655…2a6f
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x0f94e353…1f32
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
21 conflicts on slot 0x5871b087c4…69587d
Audit this contract →
← previous block·next block →recent activity