← previous blocknext block →recent activity
Analyzing
Block #106,163,687
22 transactions · 22 stateful · 2026-09-19 11:20:50 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
2.18
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,163,687 · 22 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
1w02w13w04w18w19w210w311w414w515w616w617w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9fdc204…0e30
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x9430e759…86df
0x34b655…2a6f
10 touches
10 conflicts
0x6b267bdf…b173
0x34b655…2a6f
10 touches
10 conflicts
0x222277a8…9034
0x34b655…2a6f
8 touches
6 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0xa35509fa…5cb3
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
36 conflicts on slot 0xd9fdc2041f…290e30
Audit this contract →
← previous block·next block →recent activity