← previous blocknext block →recent activity
Analyzing
Block #87,665,411
15 transactions · 13 stateful · 2026-07-14 08:37:44 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,665,411 · 15 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
1w02w13w04w26w37w49w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0caba47a…5357
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa37d59c6…996b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfe4e62b8…9ade
0x34b655…2a6f
6 touches
3 conflicts
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0x280117c9…f4b6
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 0x0caba47acc…5d5357
Audit this contract →
← previous block·next block →recent activity