← previous blocknext block →recent activity
Analyzing
Block #75,606,979
8 transactions · 5 stateful · 2026-05-19 11:50:07 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,606,979 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fb44ffa…8862
0x065c9d…c394
4 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x63582d98…e793
0x065c9d…c394
3 touches
1 conflict
0xc20864de…415d
0x065c9d…c394
3 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0x9dc47e28…90e4
0x065c9d…c394
2 touches
0 conflicts
0xad4349cc…e2be
0x065c9d…c394
2 touches
0 conflicts
0xd5ad83da…5a87
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 0x7fb44ffa60…488862
Audit this contract →
← previous block·next block →recent activity