← previous blocknext block →recent activity
Analyzing
Block #76,506,140
9 transactions · 9 stateful · 2026-05-23 15:40:50 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,506,140 · 9 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
1w02w04w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xcc6434bd…6d5c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3da78bb9…6ebd
0x065c9d…c394
2 touches
0 conflicts
0xa4cc43e1…56e1
0x065c9d…c394
2 touches
0 conflicts
0xc236d1cd…899c
0x065c9d…c394
2 touches
0 conflicts
0xc7f9697d…ee63
0x065c9d…c394
2 touches
0 conflicts
0xe06b73b2…7b62
0x065c9d…c394
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: 0xa6afd386…b0d132
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity