← previous blocknext block →recent activity
Analyzing
Block #75,201,579
13 transactions · 11 stateful · 2026-05-17 14:33:55 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,201,579 · 13 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
2w03w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xc3a74d9f…d10c
0x065c9d…c394
4 touches
1 conflict
0x3aeaf3c0…54de
0x065c9d…c394
3 touches
1 conflict
0xe8abc8bc…8c38
0x065c9d…c394
3 touches
1 conflict
0xf7735127…1005
0x065c9d…c394
3 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c1
0x1b6862…e19c
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
3 conflicts on slot 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity