← previous blocknext block →recent activity
Analyzing
Block #76,284,071
9 transactions · 8 stateful · 2026-05-22 15:02:06 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,284,071 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xcf893cc2…d95d
0x065c9d…c394
3 touches
1 conflict
0xea6703ce…f3d8
0x065c9d…c394
3 touches
1 conflict
0x1c2aeb57…bf84
0x065c9d…c394
2 touches
0 conflicts
0x40934bfc…ce33
0x065c9d…c394
2 touches
0 conflicts
0x5b26d957…6ffc
0x065c9d…c394
2 touches
0 conflicts
0xd07c30c7…dfe5
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 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity