← previous blocknext block →recent activity
Analyzing
Block #106,389,603
17 transactions · 17 stateful · 2026-09-20 06:17:51 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,389,603 · 17 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
1w02w13w29w010w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba33378a…f1df
0x34b655…2a6f
16 touches
28 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0xda43ef99…b093
0x34b655…2a6f
8 touches
6 conflicts
0x7d8688d3…d0a3
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x8321461e…4171
0x34b655…2a6f
6 touches
3 conflicts
0xb42f28b5…5a24
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
28 conflicts on slot 0xba33378abc…73f1df
Audit this contract →
← previous block·next block →recent activity