← previous blocknext block →recent activity
Analyzing
Block #106,539,606
27 transactions · 26 stateful · 2026-09-20 18:52:51 UTC
Parallelism
70/100
Blocked
65%
Avg conflicts / tx
1.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,539,606 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w09w110w212w115w116w218w319w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec66c493…eef5
0x34b655…2a6f
14 touches
21 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
12 touches
15 conflicts
0x06c36e5a…0025
0xd32edf…ff58
11 touches
15 conflicts
0x4fce4826…5c16
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x0f28fb99…3d2e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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 0xec66c493a3…40eef5
Audit this contract →
← previous block·next block →recent activity