← previous blocknext block →recent activity
Analyzing
Block #87,060,348
14 transactions · 13 stateful · 2026-07-11 13:10:50 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,060,348 · 14 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
3w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dcb5d8d…5f07
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x149ea1fb…e34a
0x34b655…2a6f
4 touches
1 conflict
0x1e9d86f5…53a8
0x34b655…2a6f
4 touches
1 conflict
0x465ab390…328b
0x34b655…2a6f
4 touches
1 conflict
0x4e10ffaa…5365
0x34b655…2a6f
4 touches
1 conflict
0x5a13f403…8d04
0x34b655…2a6f
4 touches
1 conflict
0x68909233…e8d9
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 0x6dcb5d8d44…cd5f07
Audit this contract →
← previous block·next block →recent activity