← previous blocknext block →recent activity
Analyzing
Block #76,226,772
63 transactions · 58 stateful · 2026-05-22 08:40:47 UTC
Parallelism
71/100
Blocked
76%
Avg conflicts / tx
4.35
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #76,226,772 · 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
1w04w16w27w08w09w110w211w312w413w538w439w642w146w752w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
34 touches
136 conflicts
0x5648d337…a780
0x34b655…2a6f
22 touches
55 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
16 touches
28 conflicts
0xafd59af5…5257
0xc8689a…ee79
16 touches
28 conflicts
0xeb0915f1…c150
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x9b8c0271…90b1
0x34b655…2a6f
16 touches
28 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
16 touches
28 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
136 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity