← previous blocknext block →recent activity
Analyzing
Block #87,596,255
71 transactions · 44 stateful · 2026-07-14 00:55:28 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.14
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,596,255 · 71 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w015w016w023w124w225w326w028w129w238w039w142w043w145w146w247w348w449w550w651w752w856w259w1060w261w462w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
8 touches
6 conflicts
0x1b2c54a1…5a76
0x34b655…2a6f
8 touches
6 conflicts
0x13510de3…1c68
0x34b655…2a6f
6 touches
3 conflicts
0x146c718c…8a22
0x34b655…2a6f
6 touches
3 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
6 touches
3 conflicts
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity