← previous blocknext block →recent activity
Analyzing
Block #87,497,327
31 transactions · 27 stateful · 2026-07-13 13:53:00 UTC
Parallelism
81/100
Blocked
26%
Avg conflicts / tx
0.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,497,327 · 31 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
5w06w111w112w216w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe1d1f14d…3ffb
0x34b655…2a6f
6 touches
3 conflicts
0x4aa300fb…db36
0x34b655…2a6f
6 touches
3 conflicts
0x7548b289…f0dc
0x34b655…2a6f
6 touches
3 conflicts
0x7c6a17fa…e95d
0x34b655…2a6f
6 touches
3 conflicts
0xcfcb8911…e9da
0x34b655…2a6f
6 touches
3 conflicts
0x3641a6a6…67b4
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity