← previous blocknext block →recent activity
Analyzing
Block #108,501,568
25 transactions · 24 stateful · 2026-09-27 15:31:12 UTC
Parallelism
72/100
Blocked
71%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,501,568 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w39w110w211w414w415w318w219w220w324w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001c
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
12 touches
15 conflicts
0xa58b6cc6…652f
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xad601853…1d2a
0x34b655…2a6f
6 touches
3 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
6 touches
3 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)
15 conflicts on slot 0x0000000000…00001c
Audit this contract →
← previous block·next block →recent activity