← previous blocknext block →recent activity
Analyzing
Block #106,454,059
34 transactions · 29 stateful · 2026-09-20 11:42:18 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.65
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,454,059 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w16w218w319w421w522w623w725w426w827w928w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4154323…6854
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
36 conflicts on slot 0xa4154323bd…8f6854
Audit this contract →
← previous block·next block →recent activity