← previous blocknext block →recent activity
Analyzing
Block #106,109,711
32 transactions · 29 stateful · 2026-09-19 06:49:11 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,109,711 · 32 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
1w02w13w24w05w16w312w213w320w421w522w625w626w728w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a2896a0…2a0a
0x34b655…2a6f
14 touches
21 conflicts
0x740e8901…f572
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd8d828a7…b64d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x08f9abf1…10bf
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
21 conflicts on slot 0x2a2896a01b…cc2a0a
Audit this contract →
← previous block·next block →recent activity