← previous blocknext block →recent activity
Analyzing
Block #106,541,088
30 transactions · 27 stateful · 2026-09-20 19:00:18 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,541,088 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w28w09w110w111w212w313w214w319w120w322w424w525w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fec4dea…6005
0x34b655…2a6f
8 touches
6 conflicts
0xfac38cc8…fb9d
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe74f82c0…018f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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
6 conflicts on slot 0x7fec4dea7e…986005
Audit this contract →
← previous block·next block →recent activity