← previous blocknext block →recent activity
Analyzing
Block #105,851,839
17 transactions · 14 stateful · 2026-09-18 09:10:19 UTC
Parallelism
59/100
Blocked
64%
Avg conflicts / tx
1.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,851,839 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w19w210w311w412w513w616w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3c577ab…b3a1
0x34b655…2a6f
14 touches
21 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
8 touches
6 conflicts
0x382434ca…96b5
0x34b655…2a6f
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x6aa624fd…a852
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
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 0xb3c577ab15…eab3a1
Audit this contract →
← previous block·next block →recent activity