← previous blocknext block →recent activity
Analyzing
Block #87,761,215
21 transactions · 21 stateful · 2026-07-14 19:18:46 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,761,215 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x11230290…8aa2
0x34b655…2a6f
16 touches
28 conflicts
0x21a72fbb…b023
0x34b655…2a6f
16 touches
28 conflicts
0x28c62bca…b746
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x747f609d…1555
0x34b655…2a6f
16 touches
28 conflicts
0x9ae859db…2d84
0x34b655…2a6f
16 touches
28 conflicts
0xa55c4598…2988
0x34b655…2a6f
16 touches
28 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: Settlement / Helper
28 conflicts on slot 0x5b145de0a2…2e367c
Audit this contract →
← previous block·next block →recent activity