← previous blocknext block →recent activity
Analyzing
Block #75,702,220
16 transactions · 14 stateful · 2026-05-19 22:25:29 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,702,220 · 16 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
1w02w13w26w07w111w012w213w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1c913164…5c2e
0x34b655…2a6f
8 touches
6 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
6 touches
3 conflicts
0xbf33de3d…f199
0xd32edf…ff58
5 touches
3 conflicts
0x0711ec2d…d973
0x34b655…2a6f
4 touches
1 conflict
0x37cfaf01…4a46
0x34b655…2a6f
4 touches
1 conflict
0x37d49489…9309
0x34b655…2a6f
4 touches
1 conflict
0x50059a18…9b7b
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity