← previous blocknext block →recent activity
Analyzing
Block #76,090,806
24 transactions · 16 stateful · 2026-05-21 17:35:07 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,090,806 · 24 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
3w05w110w011w112w213w321w022w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ac
0x8d66a4…3095
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ad
0x8d66a4…3095
5 touches
3 conflicts
0x8a35acfb…d1a8
0x8d66a4…3095
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
6 conflicts on slot 0x8a35acfbc1…6bd1ac
Audit this contract →
← previous block·next block →recent activity