← previous blocknext block →recent activity
Analyzing
Block #76,239,177
11 transactions · 9 stateful · 2026-05-22 10:03:28 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,239,177 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0fe4c9e5…845d
0x065c9d…c394
2 touches
0 conflicts
0x4f536ee2…22c0
0x065c9d…c394
2 touches
0 conflicts
0x5dbb7c59…92bc
0x065c9d…c394
2 touches
0 conflicts
0x61dc52c6…6d04
0x065c9d…c394
2 touches
0 conflicts
0x9fe9ce62…42d9
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity