← previous blocknext block →recent activity
Analyzing
Block #111,843,179
20 transactions · 18 stateful · 2026-10-09 08:01:34 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #111,843,179 · 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
1w02w13w24w39w210w311w012w313w414w515w416w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0ade794…58ed
0x34b655…2a6f
8 touches
6 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
8 touches
6 conflicts
0x3af0dd8e…0028
0x1b6862…e19c
8 touches
6 conflicts
0x62f24482…75bf
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x175ab001…00a0
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
6 conflicts on slot 0xb0ade79404…9158ed
Audit this contract →
← previous block·next block →recent activity