← previous blocknext block →recent activity
Analyzing
Block #106,916,168
20 transactions · 20 stateful · 2026-09-22 02:29:07 UTC
Parallelism
45/100
Blocked
70%
Avg conflicts / tx
2.4
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,916,168 · 20 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w310w411w212w513w614w715w816w917w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206f4379…e08a
0x34b655…2a6f
16 touches
28 conflicts
0x799c3770…96ae
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x810a3aa2…0227
0x34b655…2a6f
12 touches
15 conflicts
0x9d4d1acf…db17
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xda6b535e…6d6c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
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
28 conflicts on slot 0x206f43799d…55e08a
Audit this contract →
← previous block·next block →recent activity