← previous blocknext block →recent activity
Analyzing
Block #75,701,628
32 transactions · 27 stateful · 2026-05-19 22:21:32 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,701,628 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w19w213w014w016w017w118w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x398c3139…e318
0xd32edf…ff58
11 touches
15 conflicts
0xb7b446d2…2006
0x34b655…2a6f
10 touches
10 conflicts
0xbc04d98e…a484
0x34b655…2a6f
8 touches
6 conflicts
0x2f7781d6…e632
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xaee2246e…842a
0x34b655…2a6f
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity