← previous blocknext block →recent activity
Analyzing
Block #76,576,030
20 transactions · 16 stateful · 2026-05-23 23:26:12 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,576,030 · 20 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
1w02w13w24w36w07w110w413w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af7d55b…9c5e
0xa6afd3…d132
8 touches
6 conflicts
0x222fc893…acc9
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
4 touches
1 conflict
0xdb067026…9eb8
0x1d1325…2305
4 touches
1 conflict
0xea7ebe9d…709e
0x1d1325…2305
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x10f5f4d8…572e
0x34b655…2a6f
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
6 conflicts on slot 0x1af7d55bb1…469c5e
Audit this contract →
← previous block·next block →recent activity