← previous blocknext block →recent activity
Analyzing
Block #76,232,934
11 transactions · 9 stateful · 2026-05-22 09:21:57 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,232,934 · 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
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x73d2b827…e943
0x065c9d…c394
4 touches
1 conflict
0x723a8f3f…cdfa
0x065c9d…c394
2 touches
0 conflicts
0xa8a6ea2c…27bc
0x065c9d…c394
2 touches
0 conflicts
0xac811ba2…ac43
0x065c9d…c394
2 touches
0 conflicts
0xcf57de7d…9676
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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