← previous blocknext block →recent activity
Analyzing
Block #75,140,574
21 transactions · 17 stateful · 2026-05-17 07:46:28 UTC
Parallelism
76/100
Blocked
59%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,140,574 · 21 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
1w03w15w06w17w28w39w212w013w315w116w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0x4d3e58e0…a2d7
0x34b655…2a6f
6 touches
3 conflicts
0x0711ec2d…d973
0x34b655…2a6f
4 touches
1 conflict
0x1b061426…38a2
0x34b655…2a6f
4 touches
1 conflict
0x62462b9e…bbd6
0x34b655…2a6f
4 touches
1 conflict
0x8b5365d3…442d
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