← previous blocknext block →recent activity
Analyzing
Block #87,587,117
88 transactions · 65 stateful · 2026-07-13 23:54:19 UTC
Parallelism
74/100
Blocked
78%
Avg conflicts / tx
3.5
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,587,117 · 88 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
1w02w13w24w35w46w57w620w631w732w833w934w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
34 touches
136 conflicts
0xd850fa12…30bd
0xd32edf…ff58
21 touches
55 conflicts
0x092832cd…7b28
0x34b655…2a6f
18 touches
36 conflicts
0x64dfceb0…c5d7
0x34b655…2a6f
16 touches
28 conflicts
0x803a7f3c…f171
0x34b655…2a6f
16 touches
28 conflicts
0xd5dbfacf…c5ec
0x34b655…2a6f
16 touches
28 conflicts
0x18e86f02…fa98
0x34b655…2a6f
16 touches
28 conflicts
0xcef70a96…db44
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
136 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity