← previous blocknext block →recent activity
Analyzing
Block #75,254,618
25 transactions · 19 stateful · 2026-05-17 20:28:02 UTC
Parallelism
76/100
Blocked
68%
Avg conflicts / tx
1.4
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,254,618 · 25 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
1w02w13w04w25w36w47w18w09w110w211w312w413w516w519w523w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xf3d7a307…4d63
0x065c9d…c394
8 touches
6 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xea57afd0…4232
0x34b655…2a6f
8 touches
6 conflicts
0x5a88fe44…5b58
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity