← previous blocknext block →recent activity
Analyzing
Block #87,622,210
27 transactions · 24 stateful · 2026-07-14 03:48:59 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,622,210 · 27 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
1w02w13w05w06w17w210w311w212w413w314w220w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac61d3a4…7da8
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0edff147…13ed
0x34b655…2a6f
4 touches
1 conflict
0x0edff147…13ee
0x34b655…2a6f
4 touches
1 conflict
0x11e5aa96…ddd7
0x34b655…2a6f
4 touches
1 conflict
0x4a80b863…bf91
0x34b655…2a6f
4 touches
1 conflict
0x6dcb5d8d…5f07
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
10 conflicts on slot 0xac61d3a497…e97da8
Audit this contract →
← previous block·next block →recent activity