← previous blocknext block →recent activity
Analyzing
Block #74,969,910
10 transactions · 10 stateful · 2026-05-16 12:47:25 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,969,910 · 10 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
3w04w16w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x520e9f3b…1ef7
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x935be89e…2b13
0x065c9d…c394
3 touches
1 conflict
0x6eb6bbb3…c761
0x065c9d…c394
3 touches
1 conflict
0x1bd3a0ff…969e
0x065c9d…c394
3 touches
1 conflict
0xb2a1c707…3bb8
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
1 conflict on slot 0x520e9f3b0c…be1ef7
Audit this contract →
← previous block·next block →recent activity