← previous blocknext block →recent activity
Analyzing
Block #98,742,752
22 transactions · 21 stateful · 2026-08-24 11:12:04 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,742,752 · 22 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
1w03w16w27w08w010w011w112w213w214w315w116w217w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x511bafbb…15be
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2dc44a74…08a6
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x4979282b…2932
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x511bafbb0b…ac15be
Audit this contract →
← previous block·next block →recent activity