← previous blocknext block →recent activity
Analyzing
Block #86,667,648
31 transactions · 29 stateful · 2026-07-09 17:26:50 UTC
Parallelism
42/100
Blocked
66%
Avg conflicts / tx
2.39
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,667,648 · 31 txs across 18 waves · depth 18
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
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w19w010w111w212w313w414w515w616w719w823w1124w1225w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x0e9a70ab…e67c
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
8 touches
6 conflicts
0x12573732…e891
0x34b655…2a6f
8 touches
6 conflicts
0x3d4584df…ffed
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity