← previous blocknext block →recent activity
Analyzing
Block #76,529,311
61 transactions · 55 stateful · 2026-05-23 18:15:01 UTC
Parallelism
71/100
Blocked
82%
Avg conflicts / tx
3.93
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #76,529,311 · 61 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w19w110w211w312w013w214w316w417w518w619w720w821w922w1023w1026w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75d17fe1…81a4
0xa6afd3…d132
30 touches
105 conflicts
0x00000000…003d
0xa6afd3…d132
28 touches
91 conflicts
0xb24a9fb5…f3d7
0xa6afd3…d132
28 touches
91 conflicts
0xdb067026…9eb8
0x1d1325…2305
28 touches
91 conflicts
0x99a21305…dffc
0x2a68ba…90c5
28 touches
91 conflicts
0x10abefc9…c9bc
0x1d1325…2305
28 touches
91 conflicts
0x2dc020c7…0697
0xc8689a…ee79
28 touches
91 conflicts
0x10d80fee…dbda
0x1d1325…2305
28 touches
91 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
105 conflicts on slot 0x75d17fe1ad…2081a4
Audit this contract →
← previous block·next block →recent activity