← previous blocknext block →recent activity
Analyzing
Block #106,535,538
38 transactions · 36 stateful · 2026-09-20 18:32:22 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
3
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,535,538 · 38 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5a25205…645c
0x1b6862…e19c
24 touches
66 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0012
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0013
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0015
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…001d
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…002d
0x1b6862…e19c
24 touches
66 conflicts
0xfca0a0cc…3281
0xd32edf…ff58
23 touches
66 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)
66 conflicts on slot 0xd5a2520591…97645c
Audit this contract →
← previous block·next block →recent activity