← previous blocknext block →recent activity
Analyzing
Block #75,333,988
9 transactions · 7 stateful · 2026-05-18 05:19:32 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,333,988 · 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
1w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x1b22c752…cc98
0x065c9d…c394
2 touches
0 conflicts
0x360bfe84…05a6
0x065c9d…c394
2 touches
0 conflicts
0x3cdbc755…db44
0x065c9d…c394
2 touches
0 conflicts
0x59b0fac8…f933
0x065c9d…c394
2 touches
0 conflicts
0xa3da5ecf…a2c1
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 0x443a3e479f…3af4a4
Audit this contract →
← previous block·next block →recent activity