← previous blocknext block →recent activity
Analyzing
Block #106,956,657
23 transactions · 22 stateful · 2026-09-22 05:52:55 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,956,657 · 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
2w04w06w110w111w212w313w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d828f7b…296f
0x34b655…2a6f
14 touches
21 conflicts
0xa0f9db1a…8c96
0x34b655…2a6f
12 touches
15 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
12 touches
15 conflicts
0x0463db49…5d05
0x34b655…2a6f
10 touches
10 conflicts
0x8d5fc820…1750
0x34b655…2a6f
8 touches
6 conflicts
0x4f4a6267…4dc6
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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
21 conflicts on slot 0x4d828f7b93…e7296f
Audit this contract →
← previous block·next block →recent activity