← previous blocknext block →recent activity
Analyzing
Block #99,586,317
19 transactions · 19 stateful · 2026-08-27 10:07:01 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,586,317 · 19 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
1w02w13w25w06w17w29w310w311w212w317w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7960be3…7f19
0x34b655…2a6f
8 touches
6 conflicts
0xb0e4d160…b655
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xece63115…b079
0x34b655…2a6f
6 touches
3 conflicts
0xdbc6e634…e167
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
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 0xb7960be3f0…c77f19
Audit this contract →
← previous block·next block →recent activity