← previous blocknext block →recent activity
Analyzing
Block #76,550,761
30 transactions · 27 stateful · 2026-05-23 20:37:58 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
2.3
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #76,550,761 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w38w49w513w625w726w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x9afde83d…0318
0xa6afd3…d132
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x99a21305…dffc
0x2a68ba…90c5
12 touches
15 conflicts
0x40970e69…da50
0x1d1325…2305
12 touches
15 conflicts
0x55012d1a…3907
0x1d1325…2305
12 touches
15 conflicts
0x2dc020c7…0697
0xc8689a…ee79
12 touches
15 conflicts
0x10d80fee…dbda
0x1d1325…2305
12 touches
15 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
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity