← previous blocknext block →recent activity
Analyzing
Block #76,225,882
79 transactions · 59 stateful · 2026-05-22 08:34:52 UTC
Parallelism
70/100
Blocked
81%
Avg conflicts / tx
3.94
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #76,225,882 · 79 txs across 24 waves · depth 24
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
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w513w118w220w325w427w530w731w863w964w1065w1166w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
34 touches
136 conflicts
0x70676fe1…88a6
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…001f
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…002f
0x1b6862…e19c
18 touches
36 conflicts
0x98067f20…59ea
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 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
136 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity