← previous blocknext block →recent activity
Analyzing
Block #106,550,373
23 transactions · 21 stateful · 2026-09-20 19:47:01 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,550,373 · 23 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
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe530b2cf…6f95
0x34b655…2a6f
16 touches
28 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
16 touches
28 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
10 touches
10 conflicts
0x67a56c8b…f955
0x34b655…2a6f
10 touches
10 conflicts
0xe5878b87…c477
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x83ba057c…7f83
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 0xe530b2cf37…e46f95
Audit this contract →
← previous block·next block →recent activity