← previous blocknext block →recent activity
Analyzing
Block #87,760,031
19 transactions · 17 stateful · 2026-07-14 19:10:50 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
2.16
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,760,031 · 19 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x9ae859db…2d84
0x34b655…2a6f
12 touches
15 conflicts
0x28c62bca…b746
0x34b655…2a6f
12 touches
15 conflicts
0x747f609d…1555
0x34b655…2a6f
12 touches
15 conflicts
0xaa643d44…2122
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0xab7a98d0…5a1a
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity