← previous blocknext block →recent activity
Analyzing
Block #75,835,883
9 transactions · 6 stateful · 2026-05-20 13:15:49 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,835,883 · 9 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
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x02b35f1a…1c4a
0x065c9d…c394
2 touches
0 conflicts
0x3779fb80…6134
0x065c9d…c394
2 touches
0 conflicts
0x39767d5a…b6b0
0x065c9d…c394
2 touches
0 conflicts
0xeccc460a…c014
0x065c9d…c394
2 touches
0 conflicts
0xf6a6ce8a…388c
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 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity