← previous blocknext block →recent activity
Analyzing
Block #107,982,514
14 transactions · 14 stateful · 2026-09-25 19:58:58 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,982,514 · 14 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
1w02w13w24w35w28w19w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x2ce2d49e…d187
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xeb1aa855…0938
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x1fb37a…a010
6 touches
3 conflicts
0x00000000…0009
0x1fb37a…a010
6 touches
3 conflicts
0xe569004f…0228
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
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)
10 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity