← previous blocknext block →recent activity
Analyzing
Block #75,843,424
10 transactions · 9 stateful · 2026-05-20 14:06:34 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,843,424 · 10 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
1w03w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x1598b17a…35e6
0x065c9d…c394
2 touches
0 conflicts
0x5daf4d4e…d984
0x065c9d…c394
2 touches
0 conflicts
0x8c27673e…f993
0x065c9d…c394
2 touches
0 conflicts
0xa4a47e79…a9b1
0x065c9d…c394
2 touches
0 conflicts
0xb0bc6eb8…7e90
0x065c9d…c394
2 touches
0 conflicts
0xcc4f1f14…aa5f
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