← previous blocknext block →recent activity
Analyzing
Block #75,730,615
11 transactions · 9 stateful · 2026-05-20 01:34:39 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,730,615 · 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
0xa6ba8fb5…5e2d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe6dbdcdc…eacc
0x065c9d…c394
4 touches
1 conflict
0xeb8e6823…eb9c
0x065c9d…c394
3 touches
1 conflict
0x589ac417…9cb5
0x065c9d…c394
3 touches
1 conflict
0xefb97e5c…6bcf
0x065c9d…c394
3 touches
1 conflict
0x35c8282a…b7bc
0x065c9d…c394
3 touches
1 conflict
0xcc4f1f14…aa5f
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 0xa6ba8fb5bc…465e2d
Audit this contract →
← previous block·next block →recent activity