← previous blocknext block →recent activity
Analyzing
Block #86,444,265
38 transactions · 36 stateful · 2026-07-08 16:31:04 UTC
Parallelism
60/100
Blocked
67%
Avg conflicts / tx
2.18
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,444,265 · 38 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
1w02w14w26w37w49w010w111w212w313w414w515w616w717w819w924w225w426w332w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc68d6f14…bdde
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xa3e06ffb…6c2b
0x34b655…2a6f
8 touches
6 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
8 touches
6 conflicts
0xb46ee126…a1a5
0x34b655…2a6f
8 touches
6 conflicts
0xc03846bb…73b3
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity