← previous blocknext block →recent activity
Analyzing
Block #76,116,641
8 transactions · 7 stateful · 2026-05-21 20:27:15 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,116,641 · 8 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
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x4861b8e3…eda5
0x065c9d…c394
2 touches
0 conflicts
0x7cd1947d…fe13
0x065c9d…c394
2 touches
0 conflicts
0x8fc3cb51…dad8
0x065c9d…c394
2 touches
0 conflicts
0xa775fae2…b18b
0x065c9d…c394
2 touches
0 conflicts
0xee8e4d74…707b
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