← previous blocknext block →recent activity
Analyzing
Block #76,089,211
63 transactions · 38 stateful · 2026-05-21 17:24:31 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
2.06
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #76,089,211 · 63 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
2w06w09w110w011w112w013w214w129w331w232w033w134w235w336w437w538w639w740w841w944w1257w1460w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedb848fe…6534
0x34b655…2a6f
26 touches
78 conflicts
0x313f2565…5b00
0x34b655…2a6f
26 touches
78 conflicts
0x57de3828…3fbb
0x34b655…2a6f
26 touches
78 conflicts
0xc6417de0…2191
0xc8689a…ee79
26 touches
78 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
26 touches
78 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
26 touches
78 conflicts
0x388e001a…7e04
0x34b655…2a6f
24 touches
66 conflicts
0xd74ba656…ec05
0x34b655…2a6f
20 touches
45 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: Perpl
78 conflicts on slot 0xedb848fed2…6e6534
Audit this contract →
← previous block·next block →recent activity