← previous blocknext block →recent activity
Analyzing
Block #75,105,313
9 transactions · 7 stateful · 2026-05-17 03:51:12 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,105,313 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xfec27caf…db4b
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1de2832f…9f90
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x3d7666d5…2089
0x065c9d…c394
2 touches
0 conflicts
0xb728db10…a37d
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 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity