← previous blocknext block →recent activity
Analyzing
Block #86,746,998
22 transactions · 21 stateful · 2026-07-10 02:16:46 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.27
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,746,998 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w111w212w313w417w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x157dbfb2…4089
0x34b655…2a6f
10 touches
10 conflicts
0x1ebe108b…72a0
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xba4d47a9…0d84
0x34b655…2a6f
10 touches
10 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
10 touches
10 conflicts
0xd58b9a66…1c23
0x34b655…2a6f
10 touches
10 conflicts
0x01a08f7d…dec6
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity