← previous blocknext block →recent activity
Analyzing
Block #87,712,608
35 transactions · 33 stateful · 2026-07-14 13:53:29 UTC
Parallelism
54/100
Blocked
58%
Avg conflicts / tx
3.51
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,712,608 · 35 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w29w310w411w512w613w714w815w916w1017w1118w1219w1320w1425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0x5b145de0…367c
0xc8689a…ee79
28 touches
91 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
28 touches
91 conflicts
0x67905f6e…02a1
0x34b655…2a6f
28 touches
91 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
26 touches
78 conflicts
0xa6389d47…9a28
0x34b655…2a6f
26 touches
78 conflicts
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0x47774d48…7bac
0x34b655…2a6f
12 touches
15 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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity