← previous blocknext block →recent activity
Analyzing
Block #87,727,313
95 transactions · 59 stateful · 2026-07-14 15:32:01 UTC
Parallelism
76/100
Blocked
75%
Avg conflicts / tx
2.99
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,727,313 · 95 txs across 23 waves · depth 23
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
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w58w69w714w829w947w1069w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
40 touches
190 conflicts
0xc4de6652…13f4
0x34b655…2a6f
18 touches
36 conflicts
0x4fc84498…35ad
0xd32edf…ff58
17 touches
36 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x9ae859db…2d84
0x34b655…2a6f
16 touches
28 conflicts
0x9d869c44…33b7
0x34b655…2a6f
16 touches
28 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
16 touches
28 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
190 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity