← previous blocknext block →recent activity
Analyzing
Block #116,454,601
20 transactions · 18 stateful · 2026-10-25 11:13:03 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #116,454,601 · 20 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
1w02w13w24w36w39w010w111w212w414w515w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf34802b3…9f10
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xf9f8a78a…25f3
0x34b655…2a6f
8 touches
6 conflicts
0xbac2bcd0…0651
0xd32edf…ff58
7 touches
6 conflicts
0x294b11ce…13b7
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 0xf34802b39f…f89f10
Audit this contract →
← previous block·next block →recent activity