← previous blocknext block →recent activity
Analyzing
Block #75,833,604
20 transactions · 12 stateful · 2026-05-20 13:00:27 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,833,604 · 20 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
5w06w17w28w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x7e3d750f…04fd
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0xa48ec0df…51fb
0x065c9d…c394
2 touches
0 conflicts
0xc8e759e5…bdb3
0x065c9d…c394
2 touches
0 conflicts
0xa2056a0b…a4fc
0x188d58…ea8e
2 touches
0 conflicts
0xa2056a0b…a4fd
0x188d58…ea8e
2 touches
0 conflicts
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
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity