← previous blocknext block →recent activity
Analyzing
Block #106,934,879
24 transactions · 23 stateful · 2026-09-22 04:03:17 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,934,879 · 24 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
1w02w13w24w35w46w510w011w112w213w314w415w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x8d5fc820…1750
0x34b655…2a6f
12 touches
15 conflicts
0x6758e5b6…93ae
0x34b655…2a6f
12 touches
15 conflicts
0x4b1d433e…34ac
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x4e7eb462…b2af
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
15 conflicts on slot 0xe720a4c698…508eb0
Audit this contract →
← previous block·next block →recent activity