← previous blocknext block →recent activity
Analyzing
Block #91,773,257
19 transactions · 18 stateful · 2026-07-31 00:30:14 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,773,257 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w37w28w311w412w415w316w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8d828a7…b64e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xa03b0650…ed4e
0xd32edf…ff58
7 touches
6 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 0xd8d828a7fd…01b64e
Audit this contract →
← previous block·next block →recent activity