← previous blocknext block →recent activity
Analyzing
Block #75,988,611
11 transactions · 9 stateful · 2026-05-21 06:14:03 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,988,611 · 11 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35060e21…aea8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x191a4691…5457
0x065c9d…c394
3 touches
1 conflict
0x438bdff7…9dcd
0x065c9d…c394
3 touches
1 conflict
0x4e5bd6a5…2084
0x065c9d…c394
2 touches
0 conflicts
0x70d6d54e…61f9
0x065c9d…c394
2 touches
0 conflicts
0x9d6545b8…a685
0x065c9d…c394
2 touches
0 conflicts
0xa3d61ee7…fb89
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 0x35060e21a9…00aea8
Audit this contract →
← previous block·next block →recent activity