← previous blocknext block →recent activity
Analyzing
Block #106,429,422
24 transactions · 23 stateful · 2026-09-20 09:38:14 UTC
Parallelism
63/100
Blocked
52%
Avg conflicts / tx
1.88
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,429,422 · 24 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
1w02w13w24w15w26w313w414w418w519w620w721w823w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec4ebaa6…7da8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xba33378a…f1df
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0xed863ec8…90d9
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
28 conflicts on slot 0xec4ebaa607…b37da8
Audit this contract →
← previous block·next block →recent activity