← previous blocknext block →recent activity
Analyzing
Block #87,497,131
21 transactions · 17 stateful · 2026-07-13 13:51:41 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,497,131 · 21 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
3w04w05w111w212w313w115w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70f21062…b6f3
0x34b655…2a6f
6 touches
3 conflicts
0x28c180e1…f1e2
0x34b655…2a6f
4 touches
1 conflict
0x3641a6a6…67b4
0x34b655…2a6f
4 touches
1 conflict
0x4940bb84…4ec2
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0x70f2106288…aeb6f3
Audit this contract →
← previous block·next block →recent activity