← previous blocknext block →recent activity
Analyzing
Block #108,700,815
28 transactions · 25 stateful · 2026-09-28 08:14:47 UTC
Parallelism
64/100
Blocked
60%
Avg conflicts / tx
1.82
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,700,815 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w818w226w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec85b41e…7c90
0x1b6862…e19c
18 touches
36 conflicts
0xed49ab2d…02b0
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0018
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0028
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0051
0x1b6862…e19c
18 touches
36 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)
36 conflicts on slot 0xec85b41e7d…047c90
Audit this contract →
← previous block·next block →recent activity