← previous blocknext block →recent activity
Analyzing
Block #87,715,391
40 transactions · 36 stateful · 2026-07-14 14:12:09 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.38
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,715,391 · 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
1w02w13w24w36w47w58w09w510w112w013w119w120w233w134w236w837w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x5b1d3a4d…c990
0xd32edf…ff58
11 touches
15 conflicts
0xa558e115…fc88
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x2385516f…eca5
0x34b655…2a6f
6 touches
3 conflicts
0x5e3a31d1…7a6e
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity