← previous blocknext block →recent activity
Analyzing
Block #87,317,971
28 transactions · 27 stateful · 2026-07-12 17:53:34 UTC
Parallelism
61/100
Blocked
67%
Avg conflicts / tx
2.21
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,317,971 · 28 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
1w02w13w25w06w17w08w19w210w311w412w513w617w719w220w821w323w824w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0xa05444cf…cd70
0x34b655…2a6f
10 touches
10 conflicts
0x61377ba1…0bef
0xa6afd3…d132
8 touches
6 conflicts
0xad0c145d…72b3
0xa6afd3…d132
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0178c2de…b37d
0xb1dbf0…c0d3
8 touches
6 conflicts
0x94ba9c4a…41d8
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity