← previous blocknext block →recent activity
Analyzing
Block #87,664,197
23 transactions · 19 stateful · 2026-07-14 08:29:36 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,664,197 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w310w411w512w613w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
14 touches
21 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
12 touches
15 conflicts
0x3151b440…d0aa
0x34b655…2a6f
12 touches
15 conflicts
0x47774d48…7bac
0x34b655…2a6f
12 touches
15 conflicts
0x9fd37234…2731
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5eb
0x34b655…2a6f
12 touches
15 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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity