← previous blocknext block →recent activity
Analyzing
Block #86,928,971
31 transactions · 27 stateful · 2026-07-10 22:33:01 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,928,971 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w010w011w212w013w117w218w120w121w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x25de453d…9573
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0b277fb8…2d81
0x34b655…2a6f
4 touches
1 conflict
0x0b277fb8…2d82
0x34b655…2a6f
4 touches
1 conflict
0x1c503794…b0da
0x34b655…2a6f
4 touches
1 conflict
0x2ad76970…2bd8
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
6 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity