← previous blocknext block →recent activity
Analyzing
Block #75,863,421
23 transactions · 19 stateful · 2026-05-20 16:20:40 UTC
Parallelism
52/100
Blocked
68%
Avg conflicts / tx
1.83
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #75,863,421 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w38w09w410w511w612w113w319w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
10 touches
10 conflicts
0xd49762c9…1359
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x578e7f66…1b56
0x34b655…2a6f
8 touches
6 conflicts
0x0a809ce1…7894
0x34b655…2a6f
6 touches
3 conflicts
0x5728edaf…f1d4
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity