← previous blocknext block →recent activity
Analyzing
Block #99,874,601
29 transactions · 28 stateful · 2026-08-28 10:28:31 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,874,601 · 29 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
1w02w13w04w05w06w17w28w310w312w115w216w318w321w227w128w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21a1d259…eda5
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92399d5f…5846
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfd2b6842…2753
0x34b655…2a6f
6 touches
3 conflicts
0xdbd174e4…b6f8
0x34b655…2a6f
6 touches
3 conflicts
0xf039e2f8…3d8a
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
6 conflicts on slot 0x21a1d2596d…58eda5
Audit this contract →
← previous block·next block →recent activity