← previous blocknext block →recent activity
Analyzing
Block #98,082,350
27 transactions · 24 stateful · 2026-08-22 03:12:35 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,082,350 · 27 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
1w02w13w07w08w09w110w211w313w014w115w216w217w218w320w021w124w025w326w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x9aa7036b…a2a7
0xa6afd3…d132
8 touches
6 conflicts
0x2a5499c6…0abf
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xb575cf74…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0x4d1b3b3a…468b
0xa6afd3…d132
5 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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity