← previous blocknext block →recent activity
Analyzing
Block #87,318,567
18 transactions · 14 stateful · 2026-07-12 17:57:33 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,318,567 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w27w311w212w413w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e1cd42e…1f23
0x34b655…2a6f
8 touches
6 conflicts
0x0692388c…8f27
0x34b655…2a6f
6 touches
3 conflicts
0x2f93a9d2…dd6d
0x34b655…2a6f
6 touches
3 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
6 touches
3 conflicts
0x4eb86876…c144
0x34b655…2a6f
6 touches
3 conflicts
0x6167486f…db40
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
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 0x6e1cd42e06…971f23
Audit this contract →
← previous block·next block →recent activity