← previous blocknext block →recent activity
Analyzing
Block #76,550,723
31 transactions · 21 stateful · 2026-05-23 20:37:43 UTC
Parallelism
84/100
Blocked
43%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,550,723 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w09w115w317w418w019w120w121w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a7
0x8d66a4…3095
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x169d60cf…e576
0xa6afd3…d132
6 touches
3 conflicts
0x8a35acfb…d1a6
0x8d66a4…3095
6 touches
3 conflicts
0xdf25c89b…4666
0xd32edf…ff58
5 touches
3 conflicts
0x2ce2d49e…d18a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x10d80fee…dbda
0x1d1325…2305
4 touches
1 conflict
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: Oracle / Operator Hub
3 conflicts on slot 0x8a35acfbc1…6bd1a7
Audit this contract →
← previous block·next block →recent activity