← previous blocknext block →recent activity
Analyzing
Block #87,711,427
16 transactions · 14 stateful · 2026-07-14 13:45:35 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,711,427 · 16 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
3w04w17w08w19w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1cda18d5…31c3
0x34b655…2a6f
6 touches
3 conflicts
0x07c89683…140d
0x34b655…2a6f
4 touches
1 conflict
0x2c02c3aa…cfcd
0x34b655…2a6f
4 touches
1 conflict
0x3f42e9ff…9f62
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53d52f6f…5520
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x1cda18d562…7031c3
Audit this contract →
← previous block·next block →recent activity