← previous blocknext block →recent activity
Analyzing
Block #76,521,542
21 transactions · 14 stateful · 2026-05-23 17:23:20 UTC
Parallelism
90/100
Blocked
29%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,521,542 · 21 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
1w02w110w111w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0xa51564a5…79fc
0x065c9d…c394
4 touches
1 conflict
0x1130b72a…1e02
0xd32edf…ff58
3 touches
1 conflict
0x16eb9096…dc0f
0x065c9d…c394
3 touches
1 conflict
0xf26cf617…0284
0x065c9d…c394
3 touches
1 conflict
0x06e58dc5…44cb
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 0x77ed432f03…d6fa04
Audit this contract →
← previous block·next block →recent activity