← previous blocknext block →recent activity
Analyzing
Block #87,577,008
21 transactions · 20 stateful · 2026-07-13 22:46:42 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,577,008 · 21 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
2w04w06w17w28w39w410w111w012w014w315w419w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0x978c66ea…b1ef
0x34b655…2a6f
6 touches
3 conflicts
0xa771fb55…48d2
0x34b655…2a6f
6 touches
3 conflicts
0x5ad8135f…d8e6
0x34b655…2a6f
6 touches
3 conflicts
0x8b37f931…1b3f
0x34b655…2a6f
6 touches
3 conflicts
0xe70bdeae…f1ee
0x34b655…2a6f
6 touches
3 conflicts
0x7abe0396…ab27
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity