← previous blocknext block →recent activity
Analyzing
Block #74,204,233
9 transactions · 7 stateful · 2026-05-12 23:36:30 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,204,233 · 9 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x10b642bd…b94e
0x065c9d…c394
4 touches
1 conflict
0x07e98eea…b162
0x065c9d…c394
3 touches
1 conflict
0xb53f378b…a061
0x065c9d…c394
3 touches
1 conflict
0x04f2a40d…1ddc
0x065c9d…c394
2 touches
0 conflicts
0x333dc51f…9eda
0x065c9d…c394
2 touches
0 conflicts
0x382c5a2e…3ed1
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 0xcf3283bab2…c3c9fa
Audit this contract →
← previous block·next block →recent activity