← previous blocknext block →recent activity
Analyzing
Block #106,916,030
20 transactions · 17 stateful · 2026-09-22 02:28:25 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,916,030 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w110w111w212w313w214w315w416w317w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x518221db…65f7
0x34b655…2a6f
10 touches
10 conflicts
0x49acf7ff…912d
0x34b655…2a6f
8 touches
6 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
8 touches
6 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xcd9fdccb…9ddb
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
10 conflicts on slot 0x518221db7f…5465f7
Audit this contract →
← previous block·next block →recent activity