← previous blocknext block →recent activity
Analyzing
Block #106,565,210
24 transactions · 24 stateful · 2026-09-20 21:01:41 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.83
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,565,210 · 24 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
1w02w13w24w35w06w17w28w310w213w314w415w516w617w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe4369ff…752e
0x34b655…2a6f
14 touches
21 conflicts
0xbf756c9b…2dbd
0x34b655…2a6f
10 touches
10 conflicts
0x69411fb3…e36d
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xb0e4f69d…34e7
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x2c2761c0…476e
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 0xfe4369ff80…b5752e
Audit this contract →
← previous block·next block →recent activity