← previous blocknext block →recent activity
Analyzing
Block #75,813,861
6 transactions · 4 stateful · 2026-05-20 10:48:40 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,813,861 · 6 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
0xdb50b096…692c
0x065c9d…c394
4 touches
1 conflict
0x6a22d452…3c1c
0x065c9d…c394
3 touches
1 conflict
0x143ff55c…7622
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x06bd097c…e0ed
0x065c9d…c394
2 touches
0 conflicts
0xa1db8e1e…54b0
0x065c9d…c394
2 touches
0 conflicts
0xe5903d01…c345
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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 0xdb50b096e9…80692c
Audit this contract →
← previous block·next block →recent activity