← previous blocknext block →recent activity
Analyzing
Block #76,043,820
29 transactions · 24 stateful · 2026-05-21 12:21:31 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,043,820 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w17w29w010w111w012w113w214w315w418w019w120w221w322w423w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x7f9d7efb…6345
0xd32edf…ff58
9 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x9394e22c…3da3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xffedaa84…311b
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a6
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1a7
0x8d66a4…3095
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
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity