← previous blocknext block →recent activity
Analyzing
Block #76,095,192
29 transactions · 24 stateful · 2026-05-21 18:04:21 UTC
Parallelism
62/100
Blocked
63%
Avg conflicts / tx
1.83
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #76,095,192 · 29 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w111w012w113w214w315w416w517w618w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0x388e001a…7e04
0x34b655…2a6f
16 touches
28 conflicts
0x0711ec2d…d973
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0xd49762c9…1359
0x34b655…2a6f
10 touches
10 conflicts
0xf4da64f8…3253
0x34b655…2a6f
8 touches
6 conflicts
0x2bbc0cfb…c2bf
0x1b6862…e19c
6 touches
3 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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity