← previous blocknext block →recent activity
Analyzing
Block #87,589,782
40 transactions · 37 stateful · 2026-07-14 00:12:09 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
2.2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,589,782 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w510w627w730w434w335w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x23c34127…1f37
0xd32edf…ff58
15 touches
28 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
12 touches
15 conflicts
0xac6f24e7…c98b
0x34b655…2a6f
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
10 touches
10 conflicts
0x34d95d94…3a16
0x34b655…2a6f
10 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity