← previous blocknext block →recent activity
Analyzing
Block #106,916,286
33 transactions · 31 stateful · 2026-09-22 02:29:43 UTC
Parallelism
45/100
Blocked
68%
Avg conflicts / tx
2.3
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,916,286 · 33 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w510w611w712w813w914w1015w1116w417w1228w329w432w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
20 touches
45 conflicts
0xfc906557…ae7f
0x34b655…2a6f
14 touches
21 conflicts
0x69411fb3…e36d
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x825865a0…b736
0x34b655…2a6f
12 touches
15 conflicts
0xb0e4f69d…34e6
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
45 conflicts on slot 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity