← previous blocknext block →recent activity
Analyzing
Block #106,916,310
30 transactions · 29 stateful · 2026-09-22 02:29:50 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.47
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,916,310 · 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
1w02w13w24w310w011w112w213w314w415w516w617w718w819w928w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69411fb3…e36d
0x34b655…2a6f
16 touches
28 conflicts
0x825865a0…b736
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xb1526c23…f2b9
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x574628e9…dcc3
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
28 conflicts on slot 0x69411fb3ba…bce36d
Audit this contract →
← previous block·next block →recent activity