← previous blocknext block →recent activity
Analyzing
Block #75,621,932
25 transactions · 20 stateful · 2026-05-19 13:30:31 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,621,932 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w48w413w014w115w216w317w424w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x3293a887…4400
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x95d3869f…3fef
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity