← previous blocknext block →recent activity
Analyzing
Block #106,917,177
21 transactions · 21 stateful · 2026-09-22 02:34:11 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,917,177 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w110w011w212w313w414w315w516w620w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
10 touches
10 conflicts
0x94e7f277…471b
0x34b655…2a6f
10 touches
10 conflicts
0x275c0e25…bd08
0x34b655…2a6f
8 touches
6 conflicts
0xa0998a89…1f5a
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xe06d2b07…cdd0
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
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
10 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity