← previous blocknext block →recent activity
Analyzing
Block #106,362,364
31 transactions · 31 stateful · 2026-09-20 04:00:46 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.68
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,362,364 · 31 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
1w02w13w24w35w48w513w515w620w629w930w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf54391cd…e33c
0x34b655…2a6f
8 touches
6 conflicts
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
6 touches
3 conflicts
0xba33378a…f1df
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 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity