← previous blocknext block →recent activity
Analyzing
Block #86,813,480
24 transactions · 21 stateful · 2026-07-10 09:40:44 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,813,480 · 24 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
1w02w14w05w16w07w18w09w110w212w015w217w118w219w320w322w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x76d1e78d…7877
0x40c49f…2af0
6 touches
3 conflicts
0xc7a15219…7745
0xa6afd3…d132
6 touches
3 conflicts
0x725c0153…5f97
0x34b655…2a6f
4 touches
1 conflict
0x7da56943…9753
0x34b655…2a6f
4 touches
1 conflict
0x7e8ebc95…aded
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity