← previous blocknext block →recent activity
Analyzing
Block #88,358,044
26 transactions · 24 stateful · 2026-07-17 13:51:43 UTC
Parallelism
85/100
Blocked
63%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,358,044 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w26w07w18w09w110w213w115w216w217w318w319w323w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd6c45a31…9931
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x28681974…b88f
0xa6afd3…d132
6 touches
3 conflicts
0x756913cf…e7bd
0xa6afd3…d132
6 touches
3 conflicts
0x717645ac…b30f
0xd32edf…ff58
5 touches
3 conflicts
0x48b8d2e5…3f2f
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity