← previous blocknext block →recent activity
Analyzing
Block #75,032,885
11 transactions · 8 stateful · 2026-05-16 19:48:04 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,032,885 · 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0be0d6e…7c9f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa37e61b2…0317
0x065c9d…c394
3 touches
1 conflict
0x5d4771af…99c5
0x065c9d…c394
2 touches
0 conflicts
0x5f0feac7…5fb8
0x065c9d…c394
2 touches
0 conflicts
0xaa11de7c…6904
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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 0xc0be0d6ef8…3e7c9f
Audit this contract →
← previous block·next block →recent activity