← previous blocknext block →recent activity
Analyzing
Block #87,610,311
22 transactions · 18 stateful · 2026-07-14 02:29:26 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,610,311 · 22 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
5w06w17w011w112w213w314w417w019w120w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eeb2a30…6909
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x689d5e98…d068
0x34b655…2a6f
4 touches
1 conflict
0x69ce640b…884a
0x34b655…2a6f
4 touches
1 conflict
0x7139bf32…c881
0x34b655…2a6f
4 touches
1 conflict
0x7527802e…2ba9
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 0x0eeb2a3089…8a6909
Audit this contract →
← previous block·next block →recent activity