← previous blocknext block →recent activity
Analyzing
Block #111,060,270
17 transactions · 16 stateful · 2026-10-06 14:20:29 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #111,060,270 · 17 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
1w02w13w24w36w07w18w09w110w212w314w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x1045386d…cb86
0x1b6862…e19c
8 touches
6 conflicts
0x30d620fb…f303
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0051
0x1b6862…e19c
6 touches
3 conflicts
0x9b9fc699…0aaa
0x1b6862…e19c
6 touches
3 conflicts
0xaacc38b1…d55f
0x1b6862…e19c
6 touches
3 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: ShMonad (shMON)
6 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity