← previous blocknext block →recent activity
Analyzing
Block #87,312,968
52 transactions · 43 stateful · 2026-07-12 17:20:05 UTC
Parallelism
64/100
Blocked
72%
Avg conflicts / tx
3.46
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,312,968 · 52 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w413w014w115w216w317w018w120w121w222w337w239w1140w1241w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0xa05444cf…cd70
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
12 touches
15 conflicts
0x3ef0952c…762d
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
10 touches
10 conflicts
0xc7fced58…b52f
0xd32edf…ff58
9 touches
10 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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity