← previous blocknext block →recent activity
Analyzing
Block #87,596,258
58 transactions · 45 stateful · 2026-07-14 00:55:29 UTC
Parallelism
69/100
Blocked
67%
Avg conflicts / tx
1.91
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,596,258 · 58 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w49w013w122w023w025w026w128w129w230w331w432w533w634w735w838w141w1043w146w1350w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
14 touches
21 conflicts
0xc36fa358…24cb
0x34b655…2a6f
12 touches
15 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x26050074…6967
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xb8431b57…6825
0x34b655…2a6f
10 touches
10 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