← previous blocknext block →recent activity
Analyzing
Block #87,705,592
25 transactions · 18 stateful · 2026-07-14 13:06:32 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,705,592 · 25 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
1w02w13w27w08w19w210w311w414w017w218w323w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0x5ec64628…72e4
0x34b655…2a6f
4 touches
1 conflict
0x43fab434…896f
0xa6afd3…d132
4 touches
1 conflict
0x8fa9bc45…e08f
0xa6afd3…d132
4 touches
1 conflict
0x737acb78…fce8
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity