← previous blocknext block →recent activity
Analyzing
Block #111,931,024
21 transactions · 17 stateful · 2026-10-09 15:23:33 UTC
Parallelism
62/100
Blocked
59%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #111,931,024 · 21 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
1w02w13w24w37w28w312w415w016w118w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xfac61869…a55c
0x1b6862…e19c
10 touches
10 conflicts
0x4b76a46a…48fa
0xd32edf…ff58
9 touches
10 conflicts
0xdad20621…06b1
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xbff401a6…b269
0x1b6862…e19c
6 touches
3 conflicts
0xee641785…8bfd
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)
10 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity