← previous blocknext block →recent activity
Analyzing
Block #75,087,966
7 transactions · 6 stateful · 2026-05-17 01:55:32 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,087,966 · 7 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
1w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x591ea46b…678e
0x065c9d…c394
4 touches
1 conflict
0xda3764cc…0433
0x065c9d…c394
4 touches
1 conflict
0x94631362…414c
0x065c9d…c394
3 touches
1 conflict
0x49852548…8a3c
0x065c9d…c394
3 touches
1 conflict
0xa4f630d9…b4e3
0x065c9d…c394
3 touches
1 conflict
0x71143a76…5805
0x065c9d…c394
3 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
2 touches
0 conflicts
0xf9016dc2…56c6
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 0x591ea46b10…33678e
Audit this contract →
← previous block·next block →recent activity