← previous blocknext block →recent activity
Analyzing
Block #87,699,357
34 transactions · 31 stateful · 2026-07-14 12:24:35 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.88
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,699,357 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w18w09w111w212w313w415w516w617w721w122w223w325w826w228w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x17b720f5…ad7a
0x34b655…2a6f
10 touches
10 conflicts
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0x9cbc725a…5fba
0x34b655…2a6f
6 touches
3 conflicts
0xab774675…75f7
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity