← previous blocknext block →recent activity
Analyzing
Block #86,982,081
23 transactions · 23 stateful · 2026-07-11 04:27:53 UTC
Parallelism
74/100
Blocked
61%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,982,081 · 23 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
1w03w04w15w16w27w311w212w313w414w116w417w218w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
8 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
8 touches
6 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
6 touches
3 conflicts
0x2dec0e73…3189
0x34b655…2a6f
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0xbfdd8306…fa07
0x34b655…2a6f
6 touches
3 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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity