← previous blocknext block →recent activity
Analyzing
Block #74,285,336
10 transactions · 9 stateful · 2026-05-13 08:35:44 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,285,336 · 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
1w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bfaf01c…075d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe510bdd7…279f
0x065c9d…c394
3 touches
1 conflict
0x0ca66a94…26d7
0x065c9d…c394
3 touches
1 conflict
0x389958d5…9ab8
0x065c9d…c394
2 touches
0 conflicts
0xea7813a8…eee5
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
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 0x1bfaf01c1d…b5075d
Audit this contract →
← previous block·next block →recent activity