← previous blocknext block →recent activity
Analyzing
Block #75,525,382
9 transactions · 7 stateful · 2026-05-19 02:46:27 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,525,382 · 9 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
1w02w15w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x10d2b699…017f
0x065c9d…c394
4 touches
1 conflict
0xf5754345…5ea2
0xd32edf…ff58
3 touches
1 conflict
0x08678814…1b8d
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x459c5706…f755
0x065c9d…c394
2 touches
0 conflicts
0x6e29ecfc…9bb2
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
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 0x5f77d60791…b12c84
Audit this contract →
← previous block·next block →recent activity