← previous blocknext block →recent activity
Analyzing
Block #87,067,046
16 transactions · 15 stateful · 2026-07-11 13:55:30 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,067,046 · 16 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
1w02w18w09w110w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xb52189ea…8281
0x34b655…2a6f
6 touches
3 conflicts
0x2bc13458…e6d9
0x34b655…2a6f
4 touches
1 conflict
0x2fead171…13d6
0x34b655…2a6f
4 touches
1 conflict
0x595cbd16…dac4
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0x79ace5b6…8d37
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity