← previous blocknext block →recent activity
Analyzing
Block #108,940,335
26 transactions · 23 stateful · 2026-09-29 04:23:44 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
2.04
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,940,335 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w820w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x3b482aa4…6a20
0x1b6862…e19c
18 touches
36 conflicts
0x4225a754…7247
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0056
0x1b6862…e19c
16 touches
28 conflicts
0x5bf53391…5c6b
0x1b6862…e19c
16 touches
28 conflicts
0x8efff96a…9701
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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)
36 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity