← previous blocknext block →recent activity
Analyzing
Block #106,386,237
27 transactions · 25 stateful · 2026-09-20 06:00:55 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.48
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,386,237 · 27 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
1w02w13w24w05w16w27w38w49w510w611w712w814w315w318w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba33378a…f1df
0x34b655…2a6f
14 touches
21 conflicts
0x9660f3bd…17ce
0x34b655…2a6f
14 touches
21 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x1da7723c…80a9
0x1b6862…e19c
8 touches
6 conflicts
0x99aa7964…2f10
0x34b655…2a6f
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 0xba33378abc…73f1df
Audit this contract →
← previous block·next block →recent activity