← previous blocknext block →recent activity
Analyzing
Block #109,056,503
23 transactions · 22 stateful · 2026-09-29 14:10:53 UTC
Parallelism
78/100
Blocked
55%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,056,503 · 23 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
1w02w13w24w35w46w28w39w315w316w118w221w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21bf
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xc04cd8c3…cfd4
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0051
0x1b6862…e19c
8 touches
6 conflicts
0x063eca74…c2e2
0x1b6862…e19c
8 touches
6 conflicts
0x5c421c70…c2eb
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 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity