← previous blocknext block →recent activity
Analyzing
Block #75,469,370
17 transactions · 9 stateful · 2026-05-18 20:24:12 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,469,370 · 17 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
5w06w17w28w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a7
0x8d66a4…3095
6 touches
3 conflicts
0x35b65947…44d1
0xc8689a…ee79
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0xaa7a2fe5…1178
0x34b655…2a6f
4 touches
1 conflict
0xd32f8498…be67
0x34b655…2a6f
4 touches
1 conflict
0xe1e41849…9772
0x34b655…2a6f
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
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity