← previous blocknext block →recent activity
Analyzing
Block #75,485,403
26 transactions · 23 stateful · 2026-05-18 22:12:25 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,485,403 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w310w211w112w013w114w216w017w119w020w323w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x06e40499…165e
0x1d1325…2305
4 touches
1 conflict
0x1b60b708…5b4b
0x1d1325…2305
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity