← previous blocknext block →recent activity
Analyzing
Block #76,452,069
34 transactions · 32 stateful · 2026-05-23 09:40:43 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #76,452,069 · 34 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w08w09w110w011w112w214w015w116w217w318w419w520w621w722w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xb677b3d4…5951
0xd32edf…ff58
9 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0xaa3492db…3703
0x34b655…2a6f
8 touches
6 conflicts
0x4118bd12…924a
0x34b655…2a6f
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x80b0653d…5706
0x34b655…2a6f
6 touches
3 conflicts
0xaef9058e…322a
0x34b655…2a6f
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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity