← previous blocknext block →recent activity
Analyzing
Block #75,090,901
10 transactions · 9 stateful · 2026-05-17 02:15:10 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,090,901 · 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
1w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x3ee43e27…4f9f
0x065c9d…c394
3 touches
1 conflict
0x856b35c4…3a05
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x04f5c2b7…3747
0x065c9d…c394
2 touches
0 conflicts
0x2ecbcd2d…2692
0x065c9d…c394
2 touches
0 conflicts
0x2fe1aef1…877f
0x065c9d…c394
2 touches
0 conflicts
0x46c370a2…e446
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 0xfcb7b8b239…6bebb3
Audit this contract →
← previous block·next block →recent activity