← previous blocknext block →recent activity
Analyzing
Block #108,840,651
29 transactions · 25 stateful · 2026-09-28 20:00:34 UTC
Parallelism
66/100
Blocked
76%
Avg conflicts / tx
2.45
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,840,651 · 29 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
1w02w13w24w35w46w57w68w79w810w312w414w515w617w225w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35801c67…bcc1
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0xefe8d0e0…1629
0xd32edf…ff58
17 touches
36 conflicts
0x6f409ad9…04a3
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001b
0x1b6862…e19c
14 touches
21 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 0x35801c670c…33bcc1
Audit this contract →
← previous block·next block →recent activity