← previous blocknext block →recent activity
Analyzing
Block #87,307,276
22 transactions · 19 stateful · 2026-07-12 16:42:02 UTC
Parallelism
73/100
Blocked
32%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,307,276 · 22 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
3w04w17w28w39w411w514w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb564c7f…72f9
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3be33cca…1000
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4981d48d…e2ef
0x34b655…2a6f
4 touches
1 conflict
0x51d03c9d…57a7
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xdb564c7f1e…2172f9
Audit this contract →
← previous block·next block →recent activity