← previous blocknext block →recent activity
Analyzing
Block #76,039,662
51 transactions · 42 stateful · 2026-05-21 11:53:52 UTC
Parallelism
80/100
Blocked
67%
Avg conflicts / tx
1.65
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #76,039,662 · 51 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w19w211w312w413w514w316w417w118w636w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0xc5bd8b4f…3b8e
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0003
0x63e48b…53f2
10 touches
10 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0000
0x63e48b…53f2
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x00000000…0004
0x63e48b…53f2
10 touches
10 conflicts
0x9a555477…19a8
0x754704…b603
10 touches
10 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: 0xab35264b…1cfa38
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity