← previous blocknext block →recent activity
Analyzing
Block #106,386,402
26 transactions · 24 stateful · 2026-09-20 06:01:45 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.96
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,386,402 · 26 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
1w02w111w112w013w115w216w318w419w520w621w724w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba33378a…f1df
0x34b655…2a6f
12 touches
15 conflicts
0xfece6852…70f3
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x947bb79d…6458
0x34b655…2a6f
6 touches
3 conflicts
0x33365a6a…7e0b
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
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 0xba33378abc…73f1df
Audit this contract →
← previous block·next block →recent activity