← previous blocknext block →recent activity
Analyzing
Block #75,078,914
14 transactions · 10 stateful · 2026-05-17 00:54:57 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,078,914 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w28w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa7e3ceaa…baa7
0x065c9d…c394
4 touches
1 conflict
0xb7d60c31…d48d
0x065c9d…c394
3 touches
1 conflict
0x915467f5…e0ef
0x065c9d…c394
3 touches
1 conflict
0xbd72f3ed…cfcd
0x065c9d…c394
3 touches
1 conflict
0x6ac39218…bf47
0x065c9d…c394
3 touches
1 conflict
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
6 conflicts on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity