← previous blocknext block →recent activity
Analyzing
Block #106,216,717
37 transactions · 32 stateful · 2026-09-19 15:47:46 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.49
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,216,717 · 37 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
1w02w13w24w35w07w29w113w316w419w520w623w724w825w926w1036w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6040987…df02
0x34b655…2a6f
18 touches
36 conflicts
0xe5f77696…34c6
0x34b655…2a6f
12 touches
15 conflicts
0xd9271601…7026
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x1c7d4fde…9c0a
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x159cff26…7665
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
36 conflicts on slot 0xe6040987fc…efdf02
Audit this contract →
← previous block·next block →recent activity