← previous blocknext block →recent activity
Analyzing
Block #99,489,876
23 transactions · 21 stateful · 2026-08-27 01:58:47 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
0.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,489,876 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w29w110w212w313w414w216w317w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdab81f51…399c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x51af0e92…4020
0x34b655…2a6f
6 touches
3 conflicts
0xd9c91db3…8ac8
0x34b655…2a6f
6 touches
3 conflicts
0x5e8223c2…c242
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xdab81f517f…41399c
Audit this contract →
← previous block·next block →recent activity