← previous blocknext block →recent activity
Analyzing
Block #74,645,758
10 transactions · 7 stateful · 2026-05-15 00:42:21 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,645,758 · 10 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
0xcc2c253d…b51e
0x065c9d…c394
4 touches
1 conflict
0x13f5ebdc…931c
0x065c9d…c394
3 touches
1 conflict
0xfbe3ac59…2c6d
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x5d82247b…e2dc
0x065c9d…c394
2 touches
0 conflicts
0x719f6e66…3eb2
0x065c9d…c394
2 touches
0 conflicts
0xf96d5064…3718
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 0xcc2c253df4…7cb51e
Audit this contract →
← previous block·next block →recent activity