← previous blocknext block →recent activity
Analyzing
Block #75,701,967
8 transactions · 7 stateful · 2026-05-19 22:23:47 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,701,967 · 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e69bd4f…767c
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xfa3223cf…f60d
0x065c9d…c394
3 touches
1 conflict
0xca1c7848…ac3a
0xd32edf…ff58
3 touches
1 conflict
0x0e96ed89…66e0
0x065c9d…c394
2 touches
0 conflicts
0x242ff4e6…8887
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
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 0x9e69bd4f56…91767c
Audit this contract →
← previous block·next block →recent activity