← previous blocknext block →recent activity
Analyzing
Block #86,776,232
45 transactions · 33 stateful · 2026-07-10 05:32:01 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
2.22
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,776,232 · 45 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w18w217w118w019w120w221w322w423w524w625w726w827w929w1130w1231w1333w235w336w341w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x25e3730b…24a9
0x34b655…2a6f
10 touches
10 conflicts
0x3a6290da…e683
0x34b655…2a6f
10 touches
10 conflicts
0x6d45dbc5…368e
0x34b655…2a6f
10 touches
10 conflicts
0x3230277c…ef39
0xc8689a…ee79
10 touches
10 conflicts
0x89999c15…fdac
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
10 touches
10 conflicts
0xcd81cc7b…8da0
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity