← previous blocknext block →recent activity
Analyzing
Block #87,049,599
10 transactions · 9 stateful · 2026-07-11 11:59:05 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,049,599 · 10 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
1w02w13w24w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x29b6ba40…3f62
0x34b655…2a6f
6 touches
3 conflicts
0x3053f66c…3a23
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
6 touches
3 conflicts
0x3b1387d3…cdc2
0x34b655…2a6f
6 touches
3 conflicts
0x48fb2063…4025
0x34b655…2a6f
6 touches
3 conflicts
0x53c922c1…1f78
0x34b655…2a6f
6 touches
3 conflicts
0x6744b90c…3187
0x34b655…2a6f
6 touches
3 conflicts
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity