← previous blocknext block →recent activity
Analyzing
Block #76,043,719
63 transactions · 47 stateful · 2026-05-21 12:20:51 UTC
Parallelism
71/100
Blocked
72%
Avg conflicts / tx
2.19
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #76,043,719 · 63 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
1w02w13w26w18w09w110w212w213w314w015w116w217w318w450w451w552w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x9394e22c…3da3
0x34b655…2a6f
12 touches
15 conflicts
0xcbe89126…b22b
0xd32edf…ff58
11 touches
15 conflicts
0x61ca6437…2142
0x34b655…2a6f
10 touches
11 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity