← previous blocknext block →recent activity
Analyzing
Block #106,471,085
18 transactions · 17 stateful · 2026-09-20 13:07:59 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,471,085 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w111w112w213w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed156c9d…5734
0x34b655…2a6f
10 touches
10 conflicts
0x82c1e7e7…e171
0x34b655…2a6f
8 touches
6 conflicts
0x17d87f0d…bfc5
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0xc389d1ff…6a00
0x34b655…2a6f
6 touches
3 conflicts
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
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
10 conflicts on slot 0xed156c9d1d…2a5734
Audit this contract →
← previous block·next block →recent activity