← previous blocknext block →recent activity
Analyzing
Block #108,574,072
21 transactions · 21 stateful · 2026-09-27 21:36:21 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,574,072 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w17w09w112w013w114w015w116w217w319w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd08f37ae…3d0b
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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)
3 conflicts on slot 0x0000000000…00001e
Audit this contract →
← previous block·next block →recent activity