← previous blocknext block →recent activity
Analyzing
Block #87,503,437
21 transactions · 18 stateful · 2026-07-13 14:33:52 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,503,437 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w28w39w010w114w215w418w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x521f03f8…dc0e
0x34b655…2a6f
10 touches
10 conflicts
0x015c28a0…37da
0x34b655…2a6f
8 touches
6 conflicts
0x0c0eefa8…3e5f
0x34b655…2a6f
8 touches
6 conflicts
0x1175233a…64e7
0x34b655…2a6f
8 touches
6 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x6eab5218…4aa1
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
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
10 conflicts on slot 0x521f03f844…eedc0e
Audit this contract →
← previous block·next block →recent activity