← previous blocknext block →recent activity
Analyzing
Block #106,568,245
21 transactions · 21 stateful · 2026-09-20 21:16:58 UTC
Parallelism
52/100
Blocked
57%
Avg conflicts / tx
1.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,568,245 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w17w29w210w211w312w413w514w615w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b267bdf…b173
0x34b655…2a6f
10 touches
10 conflicts
0x215160c9…7266
0x34b655…2a6f
10 touches
10 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
6 touches
3 conflicts
0x2c2761c0…476e
0x34b655…2a6f
6 touches
3 conflicts
0xc6615a36…3cf0
0x34b655…2a6f
6 touches
3 conflicts
0xc7a6cb97…66f1
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
10 conflicts on slot 0x6b267bdfb8…87b173
Audit this contract →
← previous block·next block →recent activity