← previous blocknext block →recent activity
Analyzing
Block #86,621,167
37 transactions · 31 stateful · 2026-07-09 12:15:06 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
2.35
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,621,167 · 37 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w18w19w010w111w212w313w414w516w419w521w123w228w730w932w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
12 touches
15 conflicts
0x87ee379a…cd9e
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xa29182a1…c12c
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity