← previous blocknext block →recent activity
Analyzing
Block #76,239,881
24 transactions · 22 stateful · 2026-05-22 10:08:08 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,239,881 · 24 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
1w02w15w16w07w28w39w010w111w412w413w514w115w016w119w222w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
10 touches
10 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77088c08…6948
0x065c9d…c394
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x58e06bab…34d2
0x1b6862…e19c
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: Kuru Exchange: Market-MON/USDC
10 conflicts on slot 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity