← previous blocknext block →recent activity
Analyzing
Block #89,857,499
10 transactions · 10 stateful · 2026-07-24 07:29:05 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,857,499 · 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
2w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x947bb79d…6458
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x459cbb60…8957
0x34b655…2a6f
4 touches
1 conflict
0x1d91df9e…e648
0x34b655…2a6f
2 touches
0 conflicts
0x20497f5e…c503
0x34b655…2a6f
2 touches
0 conflicts
0x20497f5e…c504
0x34b655…2a6f
2 touches
0 conflicts
0x248241b8…7e99
0x34b655…2a6f
2 touches
0 conflicts
0x4e58f1d6…2fca
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 0x947bb79d75…ca6458
Audit this contract →
← previous block·next block →recent activity