← previous blocknext block →recent activity
Analyzing
Block #75,841,937
10 transactions · 9 stateful · 2026-05-20 13:56:33 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,841,937 · 10 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
1w02w13w04w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0xd06cc746…27e4
0x384275…7777
4 touches
1 conflict
0xa2056a0b…a4fc
0x188d58…ea8e
4 touches
1 conflict
0xa2056a0b…a4fd
0x188d58…ea8e
4 touches
1 conflict
0x71ede89f…cd03
0x065c9d…c394
2 touches
0 conflicts
0xbba92b58…e6b5
0x065c9d…c394
2 touches
0 conflicts
0xc05efefc…9ca7
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity