← previous blocknext block →recent activity
Analyzing
Block #107,824,155
24 transactions · 18 stateful · 2026-09-25 06:41:48 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,824,155 · 24 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
1w02w13w24w37w09w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb8
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x7bae395f…eaa8
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x00000000…0009
0x125f12…a50b
6 touches
3 conflicts
0x3a663e9a…a9c7
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c8
0x508254…98bd
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