← previous blocknext block →recent activity
Analyzing
Block #87,717,587
43 transactions · 35 stateful · 2026-07-14 14:26:57 UTC
Parallelism
65/100
Blocked
66%
Avg conflicts / tx
2.88
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,717,587 · 43 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w17w210w113w014w115w216w317w418w519w620w721w822w923w1024w1125w1230w131w432w1333w535w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x7525206c…fbd5
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x13510de3…1c68
0x34b655…2a6f
14 touches
21 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
14 touches
21 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
14 touches
21 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
14 touches
21 conflicts
0x67905f6e…02a1
0x34b655…2a6f
14 touches
21 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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity