← previous blocknext block →recent activity
Analyzing
Block #87,585,250
16 transactions · 14 stateful · 2026-07-13 23:41:50 UTC
Parallelism
69/100
Blocked
57%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,585,250 · 16 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
1w02w13w24w36w07w18w210w413w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad0c7701…1d83
0x34b655…2a6f
8 touches
6 conflicts
0x25329a48…4e00
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x4a0328ea…d46c
0x34b655…2a6f
8 touches
6 conflicts
0xf65e878a…c43c
0x34b655…2a6f
8 touches
6 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
8 touches
6 conflicts
0x68f08f71…382a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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 0xad0c77011a…7c1d83
Audit this contract →
← previous block·next block →recent activity