← previous blocknext block →recent activity
Analyzing
Block #100,751,311
26 transactions · 24 stateful · 2026-08-31 12:04:49 UTC
Parallelism
77/100
Blocked
58%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,751,311 · 26 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
1w02w13w25w07w38w39w010w312w413w114w215w516w317w419w020w123w2
- 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
0x57f4fa6c…7b0f
0x34b655…2a6f
8 touches
6 conflicts
0xd53220ed…4735
0x1b6862…e19c
8 touches
6 conflicts
0xcfbd7c2d…754e
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x41c56387…a8f6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
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