← previous blocknext block →recent activity
Analyzing
Block #76,238,995
16 transactions · 14 stateful · 2026-05-22 10:02:16 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,238,995 · 16 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
1w07w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x97bb5755…757f
0xd32edf…ff58
3 touches
1 conflict
0x1303817e…d344
0x065c9d…c394
2 touches
0 conflicts
0x44a92e26…33c7
0x065c9d…c394
2 touches
0 conflicts
0x4f536ee2…22c0
0x065c9d…c394
2 touches
0 conflicts
0x500b30a4…9c61
0x065c9d…c394
2 touches
0 conflicts
0x5e343b6a…09a4
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 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity