← previous blocknext block →recent activity
Analyzing
Block #101,062,408
30 transactions · 26 stateful · 2026-09-01 14:10:15 UTC
Parallelism
70/100
Blocked
69%
Avg conflicts / tx
1.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,062,408 · 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
1w02w13w24w35w46w57w68w79w810w217w828w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0018
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0028
0x1b6862…e19c
18 touches
36 conflicts
0x794b8f81…3ea7
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0xd766e892…8cf7
0xd32edf…ff58
17 touches
36 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)
36 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity