← previous blocknext block →recent activity
Analyzing
Block #108,962,254
30 transactions · 25 stateful · 2026-09-29 06:14:46 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,962,254 · 30 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
1w02w03w16w07w110w211w312w413w516w217w018w119w221w625w329w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45364cf9…65d7
0x1b6862…e19c
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x59422fa0…0763
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0057
0x1b6862…e19c
8 touches
6 conflicts
0x366d5b8a…6166
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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 0x45364cf92a…4a65d7
Audit this contract →
← previous block·next block →recent activity