← previous blocknext block →recent activity
Analyzing
Block #86,791,939
24 transactions · 23 stateful · 2026-07-10 07:16:49 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
1.21
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,791,939 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w39w010w111w212w313w414w515w616w720w821w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
7 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xf85bdc12…5dff
0x34b655…2a6f
6 touches
3 conflicts
0x69b48224…cf14
0xd32edf…ff58
5 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