← previous blocknext block →recent activity
Analyzing
Block #87,663,951
20 transactions · 19 stateful · 2026-07-14 08:27:58 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,663,951 · 20 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
1w02w13w04w17w19w010w111w212w313w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42c7fd6d…fc6c
0x34b655…2a6f
6 touches
3 conflicts
0xb35e663e…354e
0x34b655…2a6f
6 touches
3 conflicts
0x4f4a7ac3…021c
0x34b655…2a6f
6 touches
3 conflicts
0x49f4036c…3e68
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x5c44a144…098d
0x34b655…2a6f
4 touches
1 conflict
0x806bf739…e950
0x34b655…2a6f
4 touches
1 conflict
0x886a4bd2…bc8d
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 0x42c7fd6d32…0afc6c
Audit this contract →
← previous block·next block →recent activity