← previous blocknext block →recent activity
Analyzing
Block #75,198,547
20 transactions · 16 stateful · 2026-05-17 14:13:42 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,198,547 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w511w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x1f4c677f…7308
0x34b655…2a6f
10 touches
10 conflicts
0x0711ec2d…d973
0x34b655…2a6f
8 touches
6 conflicts
0xd49762c9…1359
0x34b655…2a6f
8 touches
6 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x4f483049…3cc7
0x34b655…2a6f
8 touches
6 conflicts
0xbc3d6b37…2215
0x34b655…2a6f
6 touches
4 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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity