← previous blocknext block →recent activity
Analyzing
Block #87,408,846
29 transactions · 22 stateful · 2026-07-13 04:01:20 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,408,846 · 29 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
1w02w13w212w013w116w117w018w019w223w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x62f68a83…d99b
0xd32edf…ff58
5 touches
3 conflicts
0x4aa2bfeb…ca33
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x7314d56d…2b4b
0x34b655…2a6f
4 touches
1 conflict
0x80ce19e2…37d3
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity