← previous blocknext block →recent activity
Analyzing
Block #75,522,289
23 transactions · 15 stateful · 2026-05-19 02:25:11 UTC
Parallelism
78/100
Blocked
60%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,522,289 · 23 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
4w05w16w27w08w19w210w311w413w014w216w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1aa
0x8d66a4…3095
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a9
0x8d66a4…3095
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0x31f15766…e90b
0xd32edf…ff58
5 touches
3 conflicts
0xa605468c…1bfc
0x1d1325…2305
4 touches
1 conflict
0xc8525006…2b45
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
6 conflicts on slot 0x8a35acfbc1…6bd1aa
Audit this contract →
← previous block·next block →recent activity