← previous blocknext block →recent activity
Analyzing
Block #106,950,309
18 transactions · 18 stateful · 2026-09-22 05:20:57 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,950,309 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w09w111w212w314w415w517w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8abaacb…b80d
0x34b655…2a6f
10 touches
10 conflicts
0x385d548d…ad18
0x34b655…2a6f
8 touches
6 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x92abc9bd…b0a2
0x34b655…2a6f
6 touches
3 conflicts
0x9156d4c9…80d0
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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 0xf8abaacb72…2fb80d
Audit this contract →
← previous block·next block →recent activity