← previous blocknext block →recent activity
Analyzing
Block #107,442,701
26 transactions · 25 stateful · 2026-09-23 22:39:46 UTC
Parallelism
69/100
Blocked
72%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,442,701 · 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
1w02w13w04w15w26w37w08w09w110w112w013w114w215w319w220w321w422w523w624w725w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
16 touches
28 conflicts
0xf5dc501b…831c
0x34b655…2a6f
16 touches
28 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd739490d…821e
0x34b655…2a6f
11 touches
15 conflicts
0x8a35acfb…d1b0
0x37db7f…ec7b
8 touches
6 conflicts
0xdc9be26f…60ae
0x34b655…2a6f
7 touches
6 conflicts
0x62ca9e90…3d1a
0x34b655…2a6f
7 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
28 conflicts on slot 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity