← previous blocknext block →recent activity
Analyzing
Block #109,234,010
23 transactions · 20 stateful · 2026-09-30 05:05:11 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,234,010 · 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
1w02w13w24w35w49w011w012w117w019w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd18a8dca…452c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x305dc59f…b8cd
0xd32edf…ff58
9 touches
10 conflicts
0xa5b7d750…53dd
0x1b6862…e19c
8 touches
6 conflicts
0xd613edc7…fa44
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 0xd18a8dca96…b8452c
Audit this contract →
← previous block·next block →recent activity