← previous blocknext block →recent activity
Analyzing
Block #108,989,358
24 transactions · 22 stateful · 2026-09-29 08:31:48 UTC
Parallelism
58/100
Blocked
55%
Avg conflicts / tx
1.58
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,989,358 · 24 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
1w02w13w24w35w46w511w612w716w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe01158fd…f982
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x5dc3dddd…d1cf
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…002e
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0040
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0057
0x1b6862…e19c
12 touches
15 conflicts
0x22e1b157…d83b
0x1b6862…e19c
12 touches
15 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)
28 conflicts on slot 0xe01158fdb6…86f982
Audit this contract →
← previous block·next block →recent activity