← previous blocknext block →recent activity
Analyzing
Block #75,020,330
11 transactions · 10 stateful · 2026-05-16 18:24:29 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,020,330 · 11 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
1w02w04w17w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x9b18c273…e30b
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5be1505e…0889
0x065c9d…c394
3 touches
1 conflict
0x0354c846…6aac
0x065c9d…c394
3 touches
1 conflict
0x9db59808…28ef
0x065c9d…c394
3 touches
1 conflict
0x2b0b58a0…c752
0x065c9d…c394
3 touches
1 conflict
0x51ebe27f…a628
0x065c9d…c394
3 touches
1 conflict
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: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity