← previous blocknext block →recent activity
Analyzing
Block #106,206,941
25 transactions · 23 stateful · 2026-09-19 14:58:33 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,206,941 · 25 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
1w02w13w24w35w48w09w111w012w013w114w015w116w120w021w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6071d1d…496d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xf8643880…1b49
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
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 0xd6071d1d86…37496d
Audit this contract →
← previous block·next block →recent activity