← previous blocknext block →recent activity
Analyzing
Block #99,486,616
27 transactions · 26 stateful · 2026-08-27 01:42:22 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,486,616 · 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
5w08w09w110w111w212w213w114w216w217w322w325w026w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70d81211…f49f
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xb1856468…e84f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x70cd98d6…54bd
0x34b655…2a6f
6 touches
3 conflicts
0x9a100e05…c541
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xedd788b4…15ce
0x34b655…2a6f
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 0x70d812119d…c1f49f
Audit this contract →
← previous block·next block →recent activity