← previous blocknext block →recent activity
Analyzing
Block #76,030,197
10 transactions · 10 stateful · 2026-05-21 10:50:53 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,030,197 · 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
1w02w13w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0bb38095…9727
0x065c9d…c394
2 touches
0 conflicts
0x4223efac…63d4
0x065c9d…c394
2 touches
0 conflicts
0x7f35ddfe…d317
0x065c9d…c394
2 touches
0 conflicts
0xd4897354…813f
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 0x443a3e479f…3af4a4
Audit this contract →
← previous block·next block →recent activity