← previous blocknext block →recent activity
Analyzing
Block #99,173,149
10 transactions · 9 stateful · 2026-08-25 23:24:28 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,173,149 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70e677f5…e3bd
0x34b655…2a6f
4 touches
1 conflict
0xed8835c6…9688
0x34b655…2a6f
4 touches
1 conflict
0xafc3a21b…d25a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0d63ff4f…4f9a
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x4580d82d…d899
0x34b655…2a6f
2 touches
0 conflicts
0x4c557ee3…f3dd
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x70e677f5c0…90e3bd
Audit this contract →
← previous block·next block →recent activity