← previous blocknext block →recent activity
Analyzing
Block #87,595,813
33 transactions · 30 stateful · 2026-07-14 00:52:30 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
1.79
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,595,813 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w08w110w011w112w213w314w415w516w617w321w423w624w126w532w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x26050074…6967
0x34b655…2a6f
8 touches
6 conflicts
0x2dfde2ed…8801
0x34b655…2a6f
8 touches
6 conflicts
0x4f4a7ac3…021c
0x34b655…2a6f
8 touches
6 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
8 touches
6 conflicts
0x7c524e26…54c6
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity