← previous blocknext block →recent activity
Analyzing
Block #99,087,922
24 transactions · 23 stateful · 2026-08-25 16:15:31 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,087,922 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w38w49w510w111w318w520w021w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c49c85c…ee96
0x34b655…2a6f
8 touches
6 conflicts
0x865d9633…cdee
0xd32edf…ff58
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xd5fee5ce…8358
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd18a8dca…4529
0x1b6862…e19c
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
6 conflicts on slot 0x8c49c85c3e…afee96
Audit this contract →
← previous block·next block →recent activity