← previous blocknext block →recent activity
Analyzing
Block #75,094,122
8 transactions · 6 stateful · 2026-05-17 02:36:33 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,094,122 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a21326…d36b
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x139ae1ad…247d
0x065c9d…c394
3 touches
1 conflict
0x0bf663f7…4ba0
0x065c9d…c394
2 touches
0 conflicts
0x2cb71ff5…4e6a
0x065c9d…c394
2 touches
0 conflicts
0x6e5853f6…6be6
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x2e2214a9…fe0d
0x5d823e…89c6
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 0xb5a2132605…f6d36b
Audit this contract →
← previous block·next block →recent activity