← previous blocknext block →recent activity
Analyzing
Block #98,215,932
21 transactions · 21 stateful · 2026-08-22 14:25:23 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,215,932 · 21 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
1w02w15w010w211w012w313w115w417w018w119w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x987e2991…49cc
0x065c9d…c394
7 touches
6 conflicts
0x2c4c0d39…3c4a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x26bb6db7…f863
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x987e299100…1a49cc
Audit this contract →
← previous block·next block →recent activity