← previous blocknext block →recent activity
Analyzing
Block #108,787,365
30 transactions · 26 stateful · 2026-09-28 15:30:38 UTC
Parallelism
67/100
Blocked
62%
Avg conflicts / tx
1.67
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,787,365 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w410w111w112w514w616w517w119w224w626w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724ba0cf…01c7
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
8 touches
6 conflicts
0x3d354577…342d
0x34b655…2a6f
8 touches
6 conflicts
0x238d0a65…428b
0x37db7f…ec7b
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
8 touches
6 conflicts
0x0acbf39a…747c
0x34b655…2a6f
8 touches
6 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 0x724ba0cf22…b301c7
Audit this contract →
← previous block·next block →recent activity