← previous blocknext block →recent activity
Analyzing
Block #87,596,256
67 transactions · 57 stateful · 2026-07-14 00:55:28 UTC
Parallelism
66/100
Blocked
74%
Avg conflicts / tx
4
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,596,256 · 67 txs across 23 waves · depth 23
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
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w111w222w655w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
34 touches
136 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
30 touches
105 conflicts
0x5b145de0…367c
0xc8689a…ee79
24 touches
66 conflicts
0x13510de3…1c68
0x34b655…2a6f
24 touches
66 conflicts
0xd19c9d38…b459
0x34b655…2a6f
24 touches
66 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
24 touches
66 conflicts
0x26050074…6967
0x34b655…2a6f
24 touches
66 conflicts
0x9fd37234…2731
0x34b655…2a6f
24 touches
66 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
136 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity