← previous blocknext block →recent activity
Analyzing
Block #75,003,507
11 transactions · 9 stateful · 2026-05-16 16:32:06 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,003,507 · 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
4w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xbded59ea…b949
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0f2c1433…37ad
0x065c9d…c394
2 touches
0 conflicts
0x65c3b2cd…a1c9
0x065c9d…c394
2 touches
0 conflicts
0xbca33e35…4b9f
0x065c9d…c394
2 touches
0 conflicts
0xe649c5a8…b467
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: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity