← previous blocknext block →recent activity
Analyzing
Block #74,626,330
13 transactions · 10 stateful · 2026-05-14 22:32:55 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,626,330 · 13 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3ca1f0a…b10c
0x065c9d…c394
4 touches
1 conflict
0x4844eebb…178e
0x065c9d…c394
3 touches
1 conflict
0x1053102e…2e55
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2f8d4891…ab33
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x6ed01d45…cdaf
0x065c9d…c394
2 touches
0 conflicts
0x94dd0368…8021
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 0xd3ca1f0a73…5eb10c
Audit this contract →
← previous block·next block →recent activity