← previous blocknext block →recent activity
Analyzing
Block #75,943,789
16 transactions · 9 stateful · 2026-05-21 01:15:32 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,943,789 · 16 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
1w02w111w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x21db5344…ff57
0x065c9d…c394
2 touches
0 conflicts
0x27099f72…2f4b
0x065c9d…c394
2 touches
0 conflicts
0x4ab5cd62…0afb
0x065c9d…c394
2 touches
0 conflicts
0xa48d1057…3cdb
0x065c9d…c394
2 touches
0 conflicts
0xd6c8678e…c8e8
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
3 conflicts on slot 0xfcb7b8b239…6bebb3
Audit this contract →
← previous block·next block →recent activity