← previous blocknext block →recent activity
Analyzing
Block #76,574,801
20 transactions · 17 stateful · 2026-05-23 23:18:02 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,574,801 · 20 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
1w02w13w04w15w26w18w29w210w011w112w213w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a5
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1a6
0x8d66a4…3095
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x001aafdc…6f07
0x34b655…2a6f
6 touches
3 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x972da85f…50b0
0x1b6862…e19c
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…6bd1a5
Audit this contract →
← previous block·next block →recent activity