← previous blocknext block →recent activity
Analyzing
Block #74,434,449
21 transactions · 17 stateful · 2026-05-14 01:08:02 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,434,449 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w15w26w37w38w415w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0x6b319071…a105
0xc8689a…ee79
8 touches
6 conflicts
0xf0f673fd…37a7
0x5d823e…89c6
6 touches
3 conflicts
0x3e4b8d9f…b8a7
0x5d823e…89c6
6 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
6 touches
3 conflicts
0x2e2214a9…fe0d
0x5d823e…89c6
6 touches
3 conflicts
0x50997ada…364d
0x5d823e…89c6
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity