← previous blocknext block →recent activity
Analyzing
Block #74,527,928
15 transactions · 11 stateful · 2026-05-14 11:32:17 UTC
Parallelism
80/100
Blocked
18%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,527,928 · 15 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
1w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x40ecd90c…10ed
0x065c9d…c394
3 touches
1 conflict
0x88e0c2d3…6a79
0x065c9d…c394
3 touches
1 conflict
0x999eba07…b27e
0x065c9d…c394
3 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x64c35644…937a
0x065c9d…c394
2 touches
0 conflicts
0x662abd76…aac5
0x065c9d…c394
2 touches
0 conflicts
0xa5995a4d…0e09
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity