← previous blocknext block →recent activity
Analyzing
Block #106,935,586
24 transactions · 24 stateful · 2026-09-22 04:06:51 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,935,586 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w19w010w111w012w113w214w315w416w517w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x469dac8d…3411
0x34b655…2a6f
12 touches
15 conflicts
0x087bd8a7…5a10
0x34b655…2a6f
12 touches
15 conflicts
0x7fc8f46e…0f75
0x34b655…2a6f
10 touches
10 conflicts
0xeb007878…5949
0x34b655…2a6f
8 touches
6 conflicts
0xe4af4c87…9964
0x34b655…2a6f
8 touches
6 conflicts
0x709e44f8…3bc5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
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
15 conflicts on slot 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity