← previous blocknext block →recent activity
Analyzing
Block #111,843,431
23 transactions · 23 stateful · 2026-10-09 08:02:50 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #111,843,431 · 23 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
1w03w15w06w19w011w114w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa28fe745…aa22
0x34b655…2a6f
16 touches
28 conflicts
0xb4839e5d…9eb8
0x34b655…2a6f
8 touches
6 conflicts
0xb0ade794…58ed
0x34b655…2a6f
6 touches
3 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
6 touches
3 conflicts
0xf72228f6…970c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0058
0x1b6862…e19c
4 touches
1 conflict
0x366d5b8a…6167
0x1b6862…e19c
4 touches
1 conflict
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
28 conflicts on slot 0xa28fe7451b…63aa22
Audit this contract →
← previous block·next block →recent activity