← previous blocknext block →recent activity
Analyzing
Block #74,506,656
12 transactions · 11 stateful · 2026-05-14 09:08:58 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,506,656 · 12 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
1w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72c6496c…c6f4
0x065c9d…c394
4 touches
1 conflict
0x29c0fcc1…93c6
0x065c9d…c394
3 touches
1 conflict
0xbb6171c8…7ec4
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xb10e92af…ab40
0x065c9d…c394
2 touches
0 conflicts
0xe4861023…ecaf
0x065c9d…c394
2 touches
0 conflicts
0x0872abbe…9c39
0x2a68ba…90c5
2 touches
0 conflicts
0x76e559a4…77fb
0x2a68ba…90c5
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 0x72c6496cb1…fdc6f4
Audit this contract →
← previous block·next block →recent activity