← previous blocknext block →recent activity
Analyzing
Block #74,310,582
7 transactions · 5 stateful · 2026-05-13 11:23:46 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,310,582 · 7 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5b4c9e6…2410
0x065c9d…c394
4 touches
1 conflict
0x702a6d03…7ae3
0x065c9d…c394
3 touches
1 conflict
0x543d911e…cbaf
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1922f308…8145
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x3076aea3…900d
0x065c9d…c394
2 touches
0 conflicts
0x30aa7db8…fbc7
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 0xa5b4c9e6b1…f32410
Audit this contract →
← previous block·next block →recent activity