← previous blocknext block →recent activity
Analyzing
Block #75,419,995
20 transactions · 18 stateful · 2026-05-18 14:55:30 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,419,995 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w010w011w112w213w315w316w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6455d1f…1029
0x754704…b603
8 touches
6 conflicts
0x0d0b2509…074d
0x3bd359…433a
8 touches
6 conflicts
0x4d42f16e…a6cd
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
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: USDC (USDC)
6 conflicts on slot 0xe6455d1fbe…eb1029
Audit this contract →
← previous block·next block →recent activity