← previous blocknext block →recent activity
Analyzing
Block #107,848,460
32 transactions · 23 stateful · 2026-09-25 08:44:07 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,848,460 · 32 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
1w02w13w24w36w013w014w117w118w220w221w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x8f738079…ec23
0x1b6862…e19c
8 touches
6 conflicts
0x573465dc…fd6e
0xd32edf…ff58
7 touches
6 conflicts
0xf75c3a6b…0568
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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…000013
Audit this contract →
← previous block·next block →recent activity