← previous blocknext block →recent activity
Analyzing
Block #75,622,132
13 transactions · 11 stateful · 2026-05-19 13:31:51 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,622,132 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w18w110w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x1a6fe604…8a4b
0x065c9d…c394
3 touches
1 conflict
0x4e3b551d…0235
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0xe1870b13…845a
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
3 conflicts on slot 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity