← previous blocknext block →recent activity
Analyzing
Block #109,144,733
16 transactions · 14 stateful · 2026-09-29 21:35:53 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,144,733 · 16 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
1w02w13w25w36w47w08w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6cb118…4ca4
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xb1c6f289…5ff1
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0052
0x1b6862…e19c
8 touches
6 conflicts
0x03e975a9…7ce1
0x1b6862…e19c
8 touches
6 conflicts
0xca2a5765…0391
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 0x0a6cb11882…264ca4
Audit this contract →
← previous block·next block →recent activity