← previous blocknext block →recent activity
Analyzing
Block #101,060,631
30 transactions · 26 stateful · 2026-09-01 14:01:19 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,060,631 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w110w011w112w313w014w118w419w521w024w426w627w728w8
- 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
0x8d47c9a4…f11a
0x1b6862…e19c
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x95c950d5…f97d
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
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