← previous blocknext block →recent activity
Analyzing
Block #87,621,797
13 transactions · 10 stateful · 2026-07-14 03:46:13 UTC
Parallelism
54/100
Blocked
60%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,621,797 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w38w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6dacce8…0666
0x34b655…2a6f
6 touches
3 conflicts
0x79e62da8…efdc
0x34b655…2a6f
6 touches
3 conflicts
0x0dddee26…7ec8
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x18e900fa…07f4
0x34b655…2a6f
4 touches
1 conflict
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0x2fac9bcf…279a
0x34b655…2a6f
4 touches
1 conflict
0x68b75835…d6f3
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
3 conflicts on slot 0xc6dacce850…e80666
Audit this contract →
← previous block·next block →recent activity