← previous blocknext block →recent activity
Analyzing
Block #110,135,269
20 transactions · 19 stateful · 2026-10-03 08:42:06 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
1.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #110,135,269 · 20 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
1w02w13w24w35w46w57w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xada193dc…5c7e
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x0b7dccbf…e9e7
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0056
0x1b6862…e19c
14 touches
21 conflicts
0x206cc6c8…0159
0x1b6862…e19c
14 touches
21 conflicts
0x6f0f03f8…f3e0
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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)
28 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity