← previous blocknext block →recent activity
Analyzing
Block #75,847,646
14 transactions · 13 stateful · 2026-05-20 14:34:55 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,847,646 · 14 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
3w04w19w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
8 touches
6 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x135c6862…9eb6
0x34b655…2a6f
4 touches
1 conflict
0x28c180e1…f1e2
0x34b655…2a6f
4 touches
1 conflict
0x2cf96c0a…538a
0x34b655…2a6f
4 touches
1 conflict
0x0bf0549f…068c
0x34b655…2a6f
4 touches
1 conflict
0x55b6a001…1e7a
0x34b655…2a6f
4 touches
1 conflict
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity