← previous blocknext block →recent activity
Analyzing
Block #75,741,795
12 transactions · 9 stateful · 2026-05-20 02:49:00 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,741,795 · 12 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
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x1e14120d…3328
0x065c9d…c394
2 touches
0 conflicts
0x24ceaa42…5afa
0x065c9d…c394
2 touches
0 conflicts
0x3838c082…5398
0x065c9d…c394
2 touches
0 conflicts
0x6309134a…87f2
0x065c9d…c394
2 touches
0 conflicts
0x90d0275a…873f
0x065c9d…c394
2 touches
0 conflicts
0xb12b4474…702d
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity