← previous blocknext block →recent activity
Analyzing
Block #108,960,558
14 transactions · 13 stateful · 2026-09-29 06:05:59 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,960,558 · 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
1w02w13w24w35w06w08w19w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xada193dc…5c7f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xefb1ca21…fd6a
0xd32edf…ff58
7 touches
6 conflicts
0xb4aa75b5…ddf1
0x34b655…2a6f
4 touches
1 conflict
0xbefdde57…cd0e
0x34b655…2a6f
4 touches
1 conflict
0xc7679110…572d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity