← previous blocknext block →recent activity
Analyzing
Block #109,170,102
32 transactions · 23 stateful · 2026-09-29 23:43:32 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,170,102 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w610w011w117w021w628w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe426f87…16fb
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0040
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0053
0x1b6862…e19c
14 touches
21 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)
21 conflicts on slot 0xfe426f8705…4d16fb
Audit this contract →
← previous block·next block →recent activity