← previous blocknext block →recent activity
Analyzing
Block #87,629,456
14 transactions · 13 stateful · 2026-07-14 04:37:29 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,629,456 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w27w08w19w110w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8ede7b5…210f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
6 touches
3 conflicts
0x9aaca373…d7c0
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x4467ecee…e95b
0x34b655…2a6f
4 touches
1 conflict
0x4af01092…a099
0x34b655…2a6f
4 touches
1 conflict
0x609e58b2…d3bb
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 0xa8ede7b52a…84210f
Audit this contract →
← previous block·next block →recent activity