← previous blocknext block →recent activity
Analyzing
Block #76,224,866
39 transactions · 31 stateful · 2026-05-22 08:28:03 UTC
Parallelism
80/100
Blocked
61%
Avg conflicts / tx
1.49
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #76,224,866 · 39 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
1w02w13w24w35w08w110w212w018w019w120w221w322w423w524w625w226w431w135w536w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x388e001a…7e04
0x34b655…2a6f
8 touches
6 conflicts
0xb3a0d95e…b537
0x34b655…2a6f
8 touches
6 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
8 touches
6 conflicts
0xcd48ff05…bc89
0xd32edf…ff58
7 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity