← previous blocknext block →recent activity
Analyzing
Block #105,921,059
14 transactions · 13 stateful · 2026-09-18 14:59:35 UTC
Parallelism
71/100
Blocked
62%
Avg conflicts / tx
0.93
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,921,059 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w19w212w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x083a8763…5a79
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0xe43bc7fc…69bb
0xd32edf…ff58
7 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)
6 conflicts on slot 0x083a876309…ce5a79
Audit this contract →
← previous block·next block →recent activity