← previous blocknext block →recent activity
Analyzing
Block #111,847,911
21 transactions · 19 stateful · 2026-10-09 08:25:22 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #111,847,911 · 21 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
1w03w04w15w06w17w18w212w313w416w017w418w519w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xa4fd1b6f…d738
0x1b6862…e19c
6 touches
3 conflicts
0x68af9140…761a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb5c8d13b…49c1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x511edd1d…87f1
0xd32edf…ff58
5 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 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity