← previous blocknext block →recent activity
Analyzing
Block #75,865,775
14 transactions · 11 stateful · 2026-05-20 16:36:18 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,865,775 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9cc607d0…c9c7
0x34b655…2a6f
4 touches
1 conflict
0xd49762c9…1359
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb80
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf85c75bc…00b5
0xa6afd3…d132
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x6eba5e7f…4b52
0x34b655…2a6f
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
1 conflict on slot 0x9cc607d097…63c9c7
Audit this contract →
← previous block·next block →recent activity