← previous blocknext block →recent activity
Analyzing
Block #99,473,699
24 transactions · 24 stateful · 2026-08-27 00:37:17 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,473,699 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w07w18w29w110w212w314w416w518w619w721w122w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57a7cf46…25d0
0x34b655…2a6f
10 touches
10 conflicts
0x548ef1da…c736
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x8ec95f2b…f4d7
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 0x57a7cf464f…ec25d0
Audit this contract →
← previous block·next block →recent activity