← previous blocknext block →recent activity
Analyzing
Block #106,932,383
28 transactions · 26 stateful · 2026-09-22 03:50:44 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,932,383 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w010w111w212w313w414w516w317w418w519w620w721w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206f4379…e08a
0x34b655…2a6f
12 touches
15 conflicts
0x51087f5a…61f7
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x803d32b5…8094
0x34b655…2a6f
10 touches
10 conflicts
0x799c3770…96ae
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc01dd830…db33
0x34b655…2a6f
6 touches
3 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 0x206f43799d…55e08a
Audit this contract →
← previous block·next block →recent activity