← previous blocknext block →recent activity
Analyzing
Block #76,212,299
10 transactions · 7 stateful · 2026-05-22 07:04:00 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,212,299 · 10 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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5df51046…d4a8
0x065c9d…c394
2 touches
0 conflicts
0x5efa12eb…e550
0x065c9d…c394
2 touches
0 conflicts
0xc083ca9c…d7cc
0x065c9d…c394
2 touches
0 conflicts
0xdd36c7ef…6d02
0x065c9d…c394
2 touches
0 conflicts
0xfbf3705c…e74c
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