← previous blocknext block →recent activity
Analyzing
Block #76,550,809
24 transactions · 17 stateful · 2026-05-23 20:38:17 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,550,809 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w112w013w114w215w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xafd59af5…5257
0xc8689a…ee79
6 touches
3 conflicts
0x384a87d5…fff4
0x34b655…2a6f
6 touches
3 conflicts
0x43676b64…6276
0x34b655…2a6f
6 touches
3 conflicts
0x4ae3b148…7ed2
0x34b655…2a6f
6 touches
3 conflicts
0x921a58d1…db22
0x34b655…2a6f
6 touches
3 conflicts
0xb86f9bd0…1799
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
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity