← previous blocknext block →recent activity
Analyzing
Block #75,949,373
59 transactions · 46 stateful · 2026-05-21 01:52:42 UTC
Parallelism
61/100
Blocked
80%
Avg conflicts / tx
3.76
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #75,949,373 · 59 txs across 23 waves · depth 23
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
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w416w417w518w642w543w644w745w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x76ceea86…576d
0xd32edf…ff58
17 touches
36 conflicts
0x7982ca1b…f8da
0x34b655…2a6f
16 touches
28 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
14 touches
21 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
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
78 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity