← previous blocknext block →recent activity
Analyzing
Block #75,199,232
17 transactions · 11 stateful · 2026-05-17 14:18:14 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,199,232 · 17 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0c40c254…80e6
0x065c9d…c394
2 touches
0 conflicts
0x3bbc5236…5c22
0x065c9d…c394
2 touches
0 conflicts
0x715f44c8…2e36
0x065c9d…c394
2 touches
0 conflicts
0xab4d16df…a1c3
0x065c9d…c394
2 touches
0 conflicts
0xe9992bd2…acf4
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