← previous blocknext block →recent activity
Analyzing
Block #106,931,212
25 transactions · 24 stateful · 2026-09-22 03:44:50 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,931,212 · 25 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
1w02w13w25w06w17w28w09w110w111w312w413w514w615w216w320w421w522w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
14 touches
21 conflicts
0xd125c3f8…99aa
0x34b655…2a6f
12 touches
15 conflicts
0x3780a34a…b50a
0x34b655…2a6f
10 touches
10 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x8727c567…8832
0x34b655…2a6f
10 touches
10 conflicts
0xd1524132…52f1
0x34b655…2a6f
8 touches
6 conflicts
0x810a3aa2…0227
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 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity