← previous blocknext block →recent activity
Analyzing
Block #75,606,880
25 transactions · 19 stateful · 2026-05-19 11:49:28 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,606,880 · 25 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
2w05w17w08w112w013w114w215w317w018w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1aa
0x8d66a4…3095
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x06e40499…165e
0x1d1325…2305
4 touches
1 conflict
0x14d15259…7553
0x1d1325…2305
4 touches
1 conflict
0x1f5a2e2b…65f1
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9353
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9354
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
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity