← previous blocknext block →recent activity
Analyzing
Block #87,718,355
46 transactions · 38 stateful · 2026-07-14 14:32:05 UTC
Parallelism
65/100
Blocked
71%
Avg conflicts / tx
3.11
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,718,355 · 46 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
1w02w13w24w35w414w015w116w217w318w419w520w621w722w823w924w1025w1126w1227w1328w1437w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0x8b818135…eff8
0x34b655…2a6f
12 touches
15 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0x1de49243…4aa3
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0x1750da27…5388
0x34b655…2a6f
10 touches
10 conflicts
0x3b17abb2…e50c
0xd32edf…ff58
9 touches
10 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