← previous blocknext block →recent activity
Analyzing
Block #111,843,183
35 transactions · 25 stateful · 2026-10-09 08:01:35 UTC
Parallelism
89/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #111,843,183 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w116w017w121w122w023w124w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf9f8a78a…25f3
0x34b655…2a6f
4 touches
1 conflict
0x62f24482…75bf
0x34b655…2a6f
4 touches
1 conflict
0xab3ad3dc…2a56
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe09e365c…b22d
0x34b655…2a6f
4 touches
1 conflict
0xf98f0ade…20c2
0x34b655…2a6f
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
6 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity