← previous blocknext block →recent activity
Analyzing
Block #76,213,379
23 transactions · 18 stateful · 2026-05-22 07:11:15 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,213,379 · 23 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
1w02w13w24w05w17w38w49w511w012w114w015w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
8 touches
6 conflicts
0xea57afd0…4232
0x34b655…2a6f
8 touches
6 conflicts
0x19f693d6…b35e
0xd32edf…ff58
7 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0x8221fa2d…f67f
0x065c9d…c394
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x47679846…4d1b
0x34b655…2a6f
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: Kuru Exchange: Market-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity