← previous blocknext block →recent activity
Analyzing
Block #87,520,311
41 transactions · 33 stateful · 2026-07-13 16:27:02 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.46
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,520,311 · 41 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w112w013w114w216w219w520w623w724w426w829w331w232w933w436w938w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0x9da42530…1c86
0x34b655…2a6f
10 touches
10 conflicts
0xc3688185…9b36
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x8a35acfb…d1a7
0x158622…375e
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a8
0x158622…375e
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity