← previous blocknext block →recent activity
Analyzing
Block #87,712,914
12 transactions · 10 stateful · 2026-07-14 13:55:31 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,712,914 · 12 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
1w02w13w25w07w19w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0ba865dd…a249
0x34b655…2a6f
4 touches
1 conflict
0x38948e75…437a
0x34b655…2a6f
4 touches
1 conflict
0x560ed681…07e6
0x34b655…2a6f
4 touches
1 conflict
0x6a1604d1…3e8a
0x34b655…2a6f
4 touches
1 conflict
0x6c2aa5be…d808
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity