← previous blocknext block →recent activity
Analyzing
Block #108,919,170
16 transactions · 13 stateful · 2026-09-29 02:36:51 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,919,170 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb538c6fa…9aea
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xabc74b1f…d5de
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0056
0x1b6862…e19c
6 touches
3 conflicts
0x8bde3b8b…e5fe
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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)
10 conflicts on slot 0xb538c6fa35…8a9aea
Audit this contract →
← previous block·next block →recent activity