← previous blocknext block →recent activity
Analyzing
Block #99,813,954
22 transactions · 21 stateful · 2026-08-28 05:22:07 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,813,954 · 22 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
3w09w010w111w212w013w316w417w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8b6d32…6601
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
6 touches
3 conflicts
0x96784e2c…cb41
0x34b655…2a6f
6 touches
3 conflicts
0xbbe37d77…c24a
0x34b655…2a6f
6 touches
3 conflicts
0xbd5c03fa…922b
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
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
10 conflicts on slot 0xcc8b6d3248…e46601
Audit this contract →
← previous block·next block →recent activity