← previous blocknext block →recent activity
Analyzing
Block #87,512,801
11 transactions · 9 stateful · 2026-07-13 15:36:35 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,512,801 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cf1f868…c5af
0x34b655…2a6f
6 touches
3 conflicts
0x1816d4a6…5ae7
0x34b655…2a6f
4 touches
1 conflict
0x18ca6535…87c1
0x34b655…2a6f
4 touches
1 conflict
0x22ce1aa0…6e58
0x34b655…2a6f
4 touches
1 conflict
0x2a90bc5b…4a86
0x34b655…2a6f
4 touches
1 conflict
0x32ddf7bb…b265
0x34b655…2a6f
4 touches
1 conflict
0x375599b1…2326
0x34b655…2a6f
4 touches
1 conflict
0x3f85f288…7c97
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 0x8cf1f86890…38c5af
Audit this contract →
← previous block·next block →recent activity