← previous blocknext block →recent activity
Analyzing
Block #75,015,310
9 transactions · 8 stateful · 2026-05-16 17:50:59 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,015,310 · 9 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb325507…4f1a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc37b60f7…add0
0x065c9d…c394
3 touches
1 conflict
0x0449fe46…cab1
0x065c9d…c394
2 touches
0 conflicts
0x4c31cb9a…82a7
0x065c9d…c394
2 touches
0 conflicts
0x5c80c745…694e
0x065c9d…c394
2 touches
0 conflicts
0xc1c22ef8…b612
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
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
1 conflict on slot 0xeb32550774…a34f1a
Audit this contract →
← previous block·next block →recent activity