← previous blocknext block →recent activity
Analyzing
Block #106,923,842
23 transactions · 22 stateful · 2026-09-22 03:07:44 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,923,842 · 23 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
4w05w16w27w38w49w210w311w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
12 touches
15 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
12 touches
15 conflicts
0x681b1d0d…2e6b
0x34b655…2a6f
10 touches
10 conflicts
0x81696049…331c
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
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
15 conflicts on slot 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity