← previous blocknext block →recent activity
Analyzing
Block #99,290,829
23 transactions · 21 stateful · 2026-08-26 09:16:37 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,290,829 · 23 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
1w02w03w18w09w110w213w214w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0xfbcccf05…6fe5
0x34b655…2a6f
6 touches
3 conflicts
0x6266e26a…96ee
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4c29ecd5…58b6
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity