← previous blocknext block →recent activity
Analyzing
Block #116,898,449
17 transactions · 16 stateful · 2026-10-27 00:27:42 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #116,898,449 · 17 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
1w02w13w24w35w48w09w010w111w212w313w014w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d43ee99…bdd7
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x9c1f5227…366f
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0055
0x1b6862…e19c
8 touches
6 conflicts
0x2ddb98bb…89f6
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 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)
10 conflicts on slot 0x6d43ee99c8…ecbdd7
Audit this contract →
← previous block·next block →recent activity