← previous blocknext block →recent activity
Analyzing
Block #76,550,808
37 transactions · 21 stateful · 2026-05-23 20:38:17 UTC
Parallelism
89/100
Blocked
48%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,550,808 · 37 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
1w02w14w25w38w010w113w214w120w224w025w134w035w236w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb86f9bd0…1799
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x0409085c…3524
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd6071d1d…496b
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
6 conflicts on slot 0xb86f9bd010…061799
Audit this contract →
← previous block·next block →recent activity