← previous blocknext block →recent activity
Analyzing
Block #106,954,368
21 transactions · 21 stateful · 2026-09-22 05:41:24 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,954,368 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w112w213w315w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x351fcb8b…49ab
0x34b655…2a6f
12 touches
15 conflicts
0x01ad5dd0…11a1
0x34b655…2a6f
10 touches
10 conflicts
0xe7f1cb38…d377
0x34b655…2a6f
8 touches
6 conflicts
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0x0bfb99f2…9779
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 0x351fcb8b6b…2349ab
Audit this contract →
← previous block·next block →recent activity