← previous blocknext block →recent activity
Analyzing
Block #87,326,288
19 transactions · 18 stateful · 2026-07-12 18:49:12 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,326,288 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w48w511w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xa8b18ba0…f380
0x34b655…2a6f
10 touches
10 conflicts
0x1ebe108b…72a0
0x34b655…2a6f
10 touches
10 conflicts
0x53da160f…7b3a
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0x5d6f58dd…5f81
0x34b655…2a6f
8 touches
6 conflicts
0x0a2287c1…aba7
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity