← previous blocknext block →recent activity
Analyzing
Block #87,524,604
20 transactions · 16 stateful · 2026-07-13 16:56:05 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,524,604 · 20 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
4w09w110w011w212w313w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0xfdd655b8…bf89
0x34b655…2a6f
8 touches
6 conflicts
0x78b7945b…2113
0x34b655…2a6f
6 touches
3 conflicts
0x4b0a67ef…b8ba
0x34b655…2a6f
4 touches
1 conflict
0x52d2a422…f1ea
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x884dd0f3…2af0
0x34b655…2a6f
4 touches
1 conflict
0x8f2d72a5…5d65
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
6 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity