← previous blocknext block →recent activity
Analyzing
Block #98,647,080
14 transactions · 13 stateful · 2026-08-24 03:01:42 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,647,080 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w09w210w111w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8782bd78…eee4
0x34b655…2a6f
6 touches
3 conflicts
0xd202536b…68cf
0xa6afd3…d132
4 touches
1 conflict
0x89bebdd6…d812
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
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
3 conflicts on slot 0x8782bd7836…0beee4
Audit this contract →
← previous block·next block →recent activity