← previous blocknext block →recent activity
Analyzing
Block #111,072,302
41 transactions · 35 stateful · 2026-10-06 15:21:12 UTC
Parallelism
83/100
Blocked
60%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #111,072,302 · 41 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
1w02w13w04w15w26w39w210w311w413w417w126w427w131w240w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004f
0x80c745…7210
10 touches
10 conflicts
0x6afc19c9…bd68
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0051
0x1b6862…e19c
8 touches
6 conflicts
0x366d5b8a…6160
0x1b6862…e19c
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: 0x80c74517…647210
10 conflicts on slot 0x0000000000…00004f
Audit this contract →
← previous block·next block →recent activity