← previous blocknext block →recent activity
Analyzing
Block #87,517,012
25 transactions · 22 stateful · 2026-07-13 16:04:48 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,517,012 · 25 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
7w08w111w013w214w315w018w019w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x8062795f…de55
0x34b655…2a6f
8 touches
6 conflicts
0xd2ff8779…689f
0x34b655…2a6f
8 touches
6 conflicts
0xa535ecc7…c0e0
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf34aa0ca…aeb6
0x34b655…2a6f
8 touches
6 conflicts
0x0f068b13…fb19
0x34b655…2a6f
8 touches
6 conflicts
0xae901867…8085
0x34b655…2a6f
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity