← previous blocknext block →recent activity
Analyzing
Block #108,494,403
15 transactions · 14 stateful · 2026-09-27 14:55:06 UTC
Parallelism
47/100
Blocked
64%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,494,403 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w110w411w512w613w714w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdce0c7b0…794a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x398c985c…810b
0x34b655…2a6f
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)
6 conflicts on slot 0x0000000000…00001c
Audit this contract →
← previous block·next block →recent activity