← previous blocknext block →recent activity
Analyzing
Block #76,529,508
26 transactions · 17 stateful · 2026-05-23 18:16:20 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,529,508 · 26 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
1w05w08w19w211w113w214w315w316w418w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc2eec079…cd4f
0xd32edf…ff58
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xb24a9fb5…f3d7
0xa6afd3…d132
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: 0xa6afd386…b0d132
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity