← previous blocknext block →recent activity
Analyzing
Block #102,110,132
25 transactions · 23 stateful · 2026-09-05 06:10:12 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
1.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,110,132 · 25 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
1w02w13w24w35w46w58w09w111w512w013w114w216w317w420w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64e1f0ce…715b
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 conflicts
0x5fda5a15…cfb6
0xd32edf…ff58
11 touches
15 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)
15 conflicts on slot 0x64e1f0ce78…4e715b
Audit this contract →
← previous block·next block →recent activity