← previous blocknext block →recent activity
Analyzing
Block #76,239,960
11 transactions · 9 stateful · 2026-05-22 10:08:39 UTC
Parallelism
64/100
Blocked
56%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,239,960 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x133e1190…5776
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x8ece40e1…6ec2
0x065c9d…c394
3 touches
1 conflict
0x346974c3…adb2
0x065c9d…c394
3 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
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
3 conflicts on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity