← previous blocknext block →recent activity
Analyzing
Block #75,839,741
59 transactions · 47 stateful · 2026-05-20 13:41:45 UTC
Parallelism
71/100
Blocked
79%
Avg conflicts / tx
2.24
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #75,839,741 · 59 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w29w318w319w220w421w422w323w524w326w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xa6e79046…af59
0xd32edf…ff58
9 touches
10 conflicts
0xd1480c90…ae0b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
8 touches
6 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